Templates create compile errors in solutions with Central Package Management (CPM)

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The project templates always add a Version attribute to the <PackageReference> items in the csproj file. This is an error when Central Package Management (CPM) is enabled.

Expected Behavior

The project templates should not add a Version attribute to the <PackageReference> items in the csproj file when Central Package Management (CPM) is enabled. If nesessary, the required <PackageVersion> items should be added to the Directory.Packages.props file.

Steps To Reproduce

1. Create or open a solution with Central Package Management (CPM)
2. Add a new project via one of the project templates that uses <PackageReference> items (e.g. by enabling individual authentication or OpenAPI support for an ASP.NET Core project).
3. Notice that there are compile errors. The root error is NU1008 Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items

Exceptions (if any)

No response

.NET Version

7.0.203

Anything else?

Using Visual Studio 17.5.5

Related: dotnet/test-templates#300

[YuliiaKovalova]

Hi @mkArtakMSFT,

The Template Engine crew is ok with your plans.

[cremor]

@YuliiaKovalova I’m not a template author. I initially created this issue in the dotnet/aspnetcore repository. It was specific about the ASP.NET Core project templates. But then it was moved to other repositories, see comments above.

So if you think that this is not a general templating engine issue, then it should be moved back to dotnet/aspnetcore.