Add WebApi-CSharp Template Toggle Description (#37367)

[captainsafia]

Description

This PR adds a clearer description to the "Enable OpenAPI" open in Web API templates.

Customer Impact

This change does not introduce any functional changes but makes it easier for customers to understand what happens when they check/uncheck the "Enable OpenAPI" item in the VS new project experience.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

This change adds more documentation and does not introduce functional changes to the UI.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

Closes #37864

[ghost]

Hi @captainsafia. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Hi @captainsafia. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[pranavkm]

Do we need to localize this text?

[captainsafia]

Do we need to localize this text?

@phenning Any guidance around how to localize here? I noticed from #30101 that it seems the localizations get inserted from the WebTools repo?

[phenning]

@captainsafia, I responded offline with a link to the generated files. Also, in a more general sense, the templates should be updated to use the new localization mechanism provided by the core template engine going forward. This would allow them to have their metadata localized within "dotnet new" and better streamline localization within Visual Studio. @vlada-shubina and @DavidKarlas should be able to give some guidance on this.

[bekir-ozturk]

Hi @captainsafia,
I will describe the process of switching to new localization format. But this will require getting all your templates localized again. With release so close, I'm not sure if there is time.

Starting .NET 7, we have an MSBuild task to ease this process. This should be the way going forward. But since this PR is about .NET 6, I won't give details here. Let me know if you need to apply this to main branch and I can help you further.

Starting .NET 6, we have Template Localizer tool to help with this. You should:

• Clone the repo to your local machine and create a branch for your changes
• Install the TemplateLocalizer tool
• Run the tool on your template folder (this will generate all the loc files on disk).
• Commit and push the changes to the repo, then merge.
• Loc team will automatically receive the loc files and provide the translations in a later PR.

You can install Template Localizer tool using:

dotnet tool install -g Microsoft.TemplateEngine.TemplateLocalizer

Run it on the root template directory using:

dotnet-template-localizer export <path_to_root_template_directory> --recursive

[captainsafia]

I responded offline with a link to the generated files. Also, in a more general sense, the templates should be updated to use the new localization mechanism provided by the core template engine going forward. This would allow them to have their metadata localized within "dotnet new" and better streamline localization within Visual Studio. @vlada-shubina and @DavidKarlas should be able to give some guidance on this.

Thanks! I've updated the localizations in the templates and created #38102 to track updating our infra.