-
-
Notifications
You must be signed in to change notification settings - Fork 8
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 support for Central Package Management #46
Comments
The SDK already supports the <Project>
<PropertyGroup>
<ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
<UsingMicrosoftCentralPackageVersionsSdk>true</UsingMicrosoftCentralPackageVersionsSdk>
</PropertyGroup>
<ItemGroup>
<PackageVersion Include="Microsoft.Net.Compilers.Toolset" Version="4.3.0" />
<PackageVersion Include="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" Version="3.6.0" />
</ItemGroup>
</Project> |
I confirm this works, thank you for your support @CZEMacLeod! |
…ng RazorLibrary to support predefined PackageVersions.
…with Version ItemGroup.
The release of NuGet 6.2.0, released with Visual Studio 2022 17.2, makes it possible to manage the versions of package references centrally in a single (or multiple, if one would wish)
Directory.Packages.props
file.See Central Package Management (CPM) on Microsoft Docs.
I've been migrating some of our projects to use CPM. Today I tried to migrate our first
Sdk="MSBuild.SDK.SystemWeb/4.0.82"
project, but I'm getting a NU1008 error:I presume MSBuild.SDK.SystemWeb would need to be updated to support this scenario?
Basically, when a
Directory.Packages.props
file is defined / used, theVersion
attribute on packagesMicrosoft.CodeDom.Providers.DotNetCompilerPlatform
andMicrosoft.Net.Compilers.Toolset
should either be removed or be updated toVersionOverride
.Could this be considered for a future, perhaps for the next release?
For the meantime, I could quite easily workaround this issue by setting property
ExcludeASPNetCompilers
totrue
:So supporting CPM is by no means an urgent feature request.
Thank you!
The text was updated successfully, but these errors were encountered: