Update VSIX to work with Dev17

[DefaultRyan]

This change updates the VSIX to target the next version of VS. Fortunately, this VSIX contains only templates and no code, so it can target both Dev16 and Dev17 fairly easily.

The prerequisite on Microsoft.VisualStudio.Component.CoreEditor was causing issues in Dev17, so I removed it. The other two prerequisites I simply extended the version range.

I tested installing it into a private build of Dev17, and verified:

• Project and item templates still function as expected.
• Was able to create a new WinUI3 project, build, and run it successfully.

[Fabi]

To run it from dev17 doesn't it also require an update to the Single-project MSIX Packaging Tools extension? Only using the ProjectReunion extension will result in a debug target error.

[DefaultRyan]

To run it from dev17 doesn't it also require an update to the Single-project MSIX Packaging Tools extension? Only using the ProjectReunion extension will result in a debug target error.

@Fabi could you elaborate on how you got the error you're referring to? I haven't seen it yet.

I tested this workflow successfully:

• Install this updated VSIX into Dev17
• Create a new project, using template "Blank App, Packaged with WAP (WinUI 3 in Desktop)
• Build project, and run with F5

I'm not what I would consider a VSIX expert, so if you have some insights I'll gladly listen. :)

[wjk]

@DefaultRyan The error @Fabi was referring to only occurs if you copy the MSIX manifest and assets out of the wapproj into the application project, add <EnablePreviewMsixTooling>true</EnablePreviewMsixTooling> to the csproj file, and then try to run the csproj. While this isn’t the default MSIX packaging behavior (yet!), it is far superior to using wapproj.

[DefaultRyan]

@Fabi and @wjk thanks. Somebody on our end is already aware of this and has the work scheduled. It's just out of scope for this particular PR.

[DefaultRyan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[sylveon]

@wjk do you know if this option works for C++ projects?

[wjk]

@sylveon I see no reason why it wouldn’t, although the IDE integration might be a bit screwy, since I don’t know if the VS bits have been tested with vcxproj as well as with csproj.

Microsoft.ProjectReunion.WinUI.nupkg contains props/targets that enable use in C++ projects. Inspection reveals that these targets include Microsoft.Build.Msix.targets if EnableMsixPreviewTooling is set to true; there is even a bit of C++-specific MSIX glue. Hope this helps!