-
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.exe restore works, and the automatic restore in VS causes build failures #6520
Comments
From the assets file it seems like the project references are not being resolved in VS. |
@AArnott I was not able to reproduce the issue the way you describe it with 27404.4.d15.6 I do still see discrepancies in the assets files but they're super weird. Namely it's project versions and an extra package in the project, Microsoft.VisualStudio.ConnectedServices.Package2, when run in CommandLine,
Versioning:
vs
I also see a discrepancy in the project name.
Commandline
Do any of these differences ring a bell? |
The For
Does that help? |
Incidentally, it doesn't repro for me with d15.6 27404.0 either. |
Yeah that makes sense. Since it's not breaking your build currently, I'll just consider it a lower priority, but I'd still like to investigate a bit more, as part of the drive to minimize differences among VS and CLI to eliminate unneeded restores. |
Hi, any chance this is related to my issue with broken NuGet restore since VS 15.6 Preview 4? |
@martinsuchan I think 15.6 - preview 5 is out thoguh, can you please try that? |
I believe this is a regression in 15.6
nuget.exe v4.3.0
VS d15.6 27401.0
When following these steps, the build should succeed.
But when you open the src\ConnectedServices\ConnectedServices.sln solution in VS and build, automatic package restore occurs, and screws up the ConnServ.UnitTests project's restored files and the build for that project ends up breaking due to missing references.
At this point, even command line builds fail. But if you run nuget restore at the command line for that project and then retry the build from the command line, it works again. But if you try to build from VS, then once again automatic package restore steps in and breaks the build again.
The project.assets.json for the broken project is very different (and much smaller) than the same file when it works properly as restored from the command line. The two files are attached below:
ConnServ.UnitTests.zip
The text was updated successfully, but these errors were encountered: