Update project template precedence values

[MackinnonBuck]

Update project template precedence values

When .NET 6 and .NET 7 are installed side-by-side, some item templates cannot be created via dotnet new. This PR fixes the issue by giving the 7.0 templates higher precedence.

Description

Attempting to run dotnet new using one of the affected project templates (e.g. "page") results in the following error:

Unable to resolve the template, the following installed templates are conflicting:
Identity                                Template Name  Short Name  Language  Precedence  Author     Package
--------------------------------------  -------------  ----------  --------  ----------  ---------  -------
Microsoft.AspNetCore.Mvc.RazorPage.6.0  Razor Page     page        C#        600         Microsoft
Microsoft.AspNetCore.Mvc.RazorPage.7.0  Razor Page     page        C#        600         Microsoft

Uninstall the template packages containing the templates to keep only one template from the list or add the template options which differentiate the template to run.

The fix is to update the "precedence" values for each template to correlate with the major version (e.g. 700 for .NET 7).

Customer Impact

Without this fix, customers would not be able to use dotnet new with any of the templates defined in Web.ItemTemplates or Web.Client.ItemTemplates if .NET 6 and .NET 7 are installed side-by-side.

Regression?

• Yes
• No

This is a new bug that occurs when .NET 6 and .NET 7 are installed side-by-side.

Risk

• High
• Medium
• Low

This PR changes a single value for each affected template configuration. We've already updated the precedence values for other templates and haven't seen any problems arise from that change.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[ghost]

Hi @MackinnonBuck. 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.

[MackinnonBuck]

@dotnet/aspnet-admins Would you be able to merge this please? Thanks.

UPDATE: There is some discussion offline about the general direction we should take with the template configuration. Let's hold off merging until that conversation concludes.

[dougbu]

I think we're ready to merge this. Agreed @MackinnonBuck❔ If yes, remove *NO MERGE*😁

[MackinnonBuck]

I agree, let's merge this. Thanks!