Open martinrrm opened 1 month ago
@martinrrm Issue is missing Type label, remember to add a Type label
Assigning to hotseat for investigation
Team Triage: Assigning to current hotseat for investigation
I am able to reproduce this issue in VS 2022 versions 17.11.2, 17.12 public preview, and internal preview.
I noticed an odd behavior, but I haven't identified the root cause yet.
referencedproject
BadRestore.sln
in Visual Studio 2022A.Prefix.Referencedproject
for a fraction of a second before it changed to referencedproject
. I didn't execute dotnet restore
in separate process.@voroninp I believe the repro has bad MSBuild syntax which I've fixed at https://github.com/voroninp/BadRestore/pull/1 and now the lock file is properly regenerated in VS for me.
@jeffkl , hi, I'll be able to check in a week. Thanks.
Internal ticket: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2172224
This is a weird bug, when you are using lock files and have a
ProjectA
referencingProjectB
and add a prefix in theDirectory.Build.props
with aPackageReference
to Nugetizer, the lock file is going to produce different outputs depending on where restore was made.VS will output something like this:
While doing a
dotnet restore
it will result in:Example Directory.Build.props:
Example ReferencedProject.csproj: