You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have an existing project with an app host using Central Package Management, adding a new test project template won't compile as the templates include package versions in the test project's csproj file, rather than adding them into Directory.Packages.props
Expected Behavior
After adding the test project, it should compile
Steps To Reproduce
Have an existing solution with an app host, using CPM
Add a test project - I used NUnit, although I imagine other test frameworks have the same issue
Exceptions (if any)
Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: NUnit.Analyzers;Aspire.Hosting.Testing;Microsoft.NET.Test.Sdk;NUnit;coverlet.collector;NUnit3TestAdapter.
Is there an existing issue for this?
Describe the bug
If you have an existing project with an app host using Central Package Management, adding a new test project template won't compile as the templates include package versions in the test project's csproj file, rather than adding them into
Directory.Packages.props
Expected Behavior
After adding the test project, it should compile
Steps To Reproduce
csproj:
Directory.Packages.Props
:Exceptions (if any)
Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: NUnit.Analyzers;Aspire.Hosting.Testing;Microsoft.NET.Test.Sdk;NUnit;coverlet.collector;NUnit3TestAdapter.
.NET Version info
Anything else?
No response
The text was updated successfully, but these errors were encountered: