-
Notifications
You must be signed in to change notification settings - Fork 258
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
nuget update still fails for new csproj format #6382
Comments
Could you try donet Cli: https://github.com/dotnet/cli ? "donet add [csproj] package [packageName]", it should update the package for PackageReference. |
Hi, I have two classic .csproj projects that use PackageReference both do not have packages.config file on one of them nuget update works, on the other it fails with "Unable to update. The project does not contain a packages.config file." |
@zhili1208 any updates on this? Here is the current behavior: The command doesn't fail or give any warnings: But if you go back into Visual Studio it's clear that certain projects were completely skipped and are still referencing the old version of the component: |
NuGet.exe commands like install or update aren't supported for |
does not update. If say 1.2.4 is installed, and a 1.2.5 is available then this command will not update to 1.2.5. If however I write:
It will change to 1.2.5. But I can't do that in my scenario, I need to update to latest version. |
What you can do then is to remove and then update:
|
When will this be resolved? What if one needs to use the
PackageReference
and cannot usepackages.config
?Details about Problem
Running:
fails with
NuGet Version: 4.4.1.4656
VS version (if appropriate): 15.5.2
MSBuild version: 15.5.180.51428 for .NET Framework
OS version (i.e. win10 v1607 (14393.321)): win10
Detailed repro steps so we can see the same problem
nuget.exe update
on any new csproj file withPackageReference
e.g.:The text was updated successfully, but these errors were encountered: