-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
error NU1008: Projects that use central package version management should not define the version on the PackageReference... #330
Comments
I also got this error when trying to build the project last week on Visual Studio 2022. I have a working version of the solution now, but I want to compare all the files I had to change before putting in a PR, to make sure I didn't change something I didn't need to when I started working on a fix for it. Edit: I remember what I did that I don't think is ready for a PR into the base repo... I just let VS add all the required packages to the default |
@XenotropicDev As I see your PR, in the csproj files you added |
I have the same issue on MacOs with build.sh script. |
Place <ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally> into Directory.Build.props file. |
I was having the same issue on Linux with build.sh, which got fixed by adding the code below to "Directory.Packages.props" <PropertyGroup>
<ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally>
</PropertyGroup> Check out the link below: |
I get an error
error NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items:...
multiple times, when I run the PowerShell scriptbuild.ps1
on Windows, but on Linux, the build withbuild.sh
script works fine.Below are the build error logs.
The text was updated successfully, but these errors were encountered: