Include "Universal Windows" in VS Project Template name

[ralarcon]

The Project Template name is replaced at build time in order to change it for each environment (loca, dev-nightly, pre-release and pro).

Updated the name in the local template and changed the builds variables to include "Universal Windows" as part of the name.

[msftclas]

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

[crutkas]

how will this work in once we start supporting xamarin?

[mrlacey]

It depends on how you want the Xamarin integration to work.

If we think about it on its own then it makes sense for an option to create Xamarin projects to be under the Cross-Platform group (see image below). In this case, it would make sense to have the bracketed suffixes to distinguish between multiple items in the single list of all templates.

If the intention is to add Xamarin[.Forms] as another option under frameworks in the current wizard, it might be weird that getting to this is via a template in the "Windows Universal" folder. It would be fine for people wanting to create a UWP app with XF ready to move to other platforms but wouldn't be great for people specifically wanting to target multiple platforms from the start.

I expect that Xamarin would prefer to have a separate template entry. I think it's the better option too, but it does raise some questions:

• Should you also be able to select Xamarin as a Framework for the UWP version?
• If targeting Xamarin.Forms as a framework, what about using other frameworks (MVVM Light, MVX, etc.) with it? as this is popular.
• If there is a cross-platform entry should that only be limited to creating Xamarin projects?
• Would both templates be installed together? Even if the machine only has one of the UWP or Xamarin tooling installed?
• and more questions for another time.... ;)

[crutkas]

Most of these should be in the XF issue.

• I think you'd be able to see Xamarin in UWP area
• the framework question comes into massive play here as a best POR. I think the wizard will need to be tweaked no matter what.
• dealing with tool detection is a great item to bring up. I didn't think about that

[crutkas]

xref #321 for XF issue

[ralarcon]

I fill more natural to have an entry under "cross platform" for xamarin; this would just run the wizard pre-filtered because I guess xamarin would have different frameworks and project types too...