ASP.NET Core Web App template should not have 2 short names defined

[vlada-shubina]

dotnet new CLI and template engine core is going to deprecate the support of having multiple short names for the template. We are cutting off from template.json schema shortly, but the template engine/dotnet new will still support it for a while (at least in .NET 6).

The main reason of this change is that short name is supposed to be unique, but names pool is limited and we don't want to encourage authors taking multiple names. @KathleenDollard can provide more details on it.
We made a discovery and identified that only ASP.NET Core Web App is using this feature (

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/RazorPagesWeb-CSharp/.template.config/template.json

Lines 15 to 18 in 028470e

	"shortName": [
	"webapp",
	"razor"
	],

).

Please consider removing multiple names from ASP.NET Core Web App template.

Note that in case the multiple short names won't be removed since next .NET preview the template will be shown in the dotnet new list as following: dotnet/templating#3191 (comment) as it has multiple short names defined. Previously only first name was shown in the list, which led to confusion as the user can instantiate the template with any of short names (i.e. dotnet new webapp and dotnet new razor are same commands), but due to razor was not listed it led to confusion why the template was instantiated successfully (see dotnet/templating#3038 for more details).

I can make PR making the actual change, in case you confirm which one of short names you prefer to keep.

[javiercn]

@vlada-shubina thanks for bringing this up.

@vlada-shubina do we have any data on what percentage of users is using webapp vs razor to create templates?

@DamianEdwards @LadyNaggaga do you have any thoughts on this?

@DamianEdwards I believe you suggested the change in the template name, are you ok if we deprecate the old one at this point?

@danroth27 in case you have context.

We would retain webapp as the template over razor

[vlada-shubina]

@javiercn unfortunately we don't have such stats available, we don't capture short name usage.
Worth to mention that razor is also mentioned in the list of templates here: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-new-sdk-templates.

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

@vlada-shubina is this 6.0 change only or should we also worry about 3.1, 5.0 and 2.1 releases too?

[danroth27]

I'm fine with this change. We use dotnet new webapp in the ASP.NET Core getting started template, so that's the one we need to keep.

[DamianEdwards]

The lack of data is unfortunate. Along with our own docs perhaps we should do some web searching to see if the older name shows up in other places we could notify.

[vlada-shubina]

@vlada-shubina is this 6.0 change only or should we also worry about 3.1, 5.0 and 2.1 releases too?

the change will be done in template engine / dotnet new CLI with .NET 6. We won't backport it to earlier releases.
afaik, this template is released in several packages (package per tfm). If you still service previous tfm versions, please consider updating it there, otherwise it will be shown as here in .NET 6 dotnet new.