Describe the Bug
https://developercommunity.visualstudio.com/t/Packages-Restore-done-by-VS-and-dotnet/10709497
When I reference NuGetizer project Rebuild action in VS causes NuGet to generate bad packages.lock.json file. See the description above. I am not 100% sure it is NuGetizer's bug, TBH.
Steps to Reproduce
See this repository: https://github.com/voroninp/BadRestore for reoridcution.
Run rebuild, then check packages.lock.json.file of BadRestore project.
Comment out the reference to NuGetizer in ReferencedProject.
Run rebuid several times, check packages.lock.json.file of BadRestore project again and see that referencedproject changed to A.Prefix.Referenced.Project.
Expected Behavior
I'd expect that Rebuild and dotnet restore --force-evaluate produce the same result.
Version Info
1.2.2


Describe the Bug
https://developercommunity.visualstudio.com/t/Packages-Restore-done-by-VS-and-dotnet/10709497
When I reference NuGetizer project Rebuild action in VS causes NuGet to generate bad
packages.lock.jsonfile. See the description above. I am not 100% sure it is NuGetizer's bug, TBH.Steps to Reproduce
See this repository: https://github.com/voroninp/BadRestore for reoridcution.
Run rebuild, then check
packages.lock.json.fileofBadRestoreproject.Comment out the reference to
NuGetizerinReferencedProject.Run rebuid several times, check
packages.lock.json.fileofBadRestoreproject again and see thatreferencedprojectchanged toA.Prefix.Referenced.Project.Expected Behavior
I'd expect that
Rebuildanddotnet restore --force-evaluateproduce the same result.Version Info
1.2.2