dotnet / aspnetcore Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the displayName
Property to Project Template Parameters
#40105
base: release/7.0-preview1
Are you sure you want to change the base?
Conversation
src/ProjectTemplates/Web.ProjectTemplates/content/WebApi-CSharp/.template.config/ide.host.json
Outdated
Show resolved
Hide resolved
displayName
sdisplayName
Property to Project Template Parameters
src/ProjectTemplates/Web.ProjectTemplates/content/WebApi-CSharp/.template.config/template.json
Outdated
Show resolved
Hide resolved
This reverts commit 05758e2.
See comments inline, one additional thing - now would be a good time to also remove all the strings.json files and the locale specific folders in the .template.config folder. Only the localize folder and the files it contains should remain.
We can do this in NET 7 because this new localization support has been shipping since 17.0 and NET 7 and later will not be supported in versions prior to Dev17, just like NET 6 templates are not supported in earlier versions as well.
Add the
displayName
Property to Project Template ParametersImproves display of project template parameters by providing an easily readable parameter name.
Currently:

After:

Description
Recent changes which enabled template localization (#38867) omitted the new
displayName
property, which led to VS using the parameter id/name instead. This is non-localized and comes in the form ofcamelCase
,UpperCamelCase
orkebab-case
.Fixes aspnet/AspNetCore-ManualTests#1154
Customer Impact
The property id/name is being used instead of a more legible property display name. This can manifest itself in
camelCase
,UpperCamelCase
orkebab-case
case like below:Regression?
Visual Studio 17 Preview 1.
Risk
Verification
Packaging changes reviewed?
The text was updated successfully, but these errors were encountered: