Open v-luzh opened 1 year ago
@v-luzh
In notes, 4, you say that it reproes on Windows as well. I am guessing, it reproes on Windows with all versions?
We only care about the latest version, so no need to try with the older versions.
This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment.
Hi, @nkolev92 we didn't try the adding package step for other dotnet version on Windows last time, just performed it on 3.1.425. Today we executed the same steps on .NET SDK 7.0.101. It also reproes on Windows as below.
May be the solution here is to follow the suggestion in the docs i.e., pass an explicit --force-evaluate option to run restore to update the lock file.
when RestoreLockedMode
is true
.
There shouldn't be a need to run force evaluate. That's really meant for floating versions and hand editing.
dotnet add package
should effectively "unlock" the same way the PM UI does that.
It still reproes on Dotnet SDK 9.0.100-rc.2.24420.21 patched with NuGet Client Dev\6.12.0.82.
NuGet Product Used
dotnet.exe
Product Version
.NET SDK 7.0.100
Worked before?
No response
Impact
It bothers me. A fix would be nice
Repro Steps & Context
Repro Steps:
1.Patch .NET SDK 7.0.100 with NuGet Client release-6.4.x\6.4.0.123 following the steps from: Patch dotnet SDK (Web view)
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
<RestoreLockedMode>true</RestoreLockedMode>
Expected:
Package installed successfully without errors.
Actual:
Another package is failed to install with the error NU1004 showing as below.
Notes: