Docs Page URL

https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#locking-dependencies

Description of the Issue

See comment from Microsoft(Chet) here dotnet/sdk#48795 (comment)

Our current recommendation for users that use lock files is to also lock their SDK versions via global.json with no rollforward, so they(sic) their entire toolchain stays in lockstep.

Discovery of this recommendation is currently hard

Suggested Fix

Add some version of: Our current recommendation for users that use lock files is to also lock their SDK versions via global.json with no rollforward, so they their entire toolchain stays in lockstep.

Ideally linking to an issue to track for when that recommendation changes or at least the specific issues which most users run into which require pinning the SDK in relation to lock-files
dotnet/aspnetcore#64897
dotnet/sdk#48795

Ideally the blog post https://devblogs.microsoft.com/dotnet/enable-repeatable-package-restores-using-a-lock-file/ is also updated

Opened related global.json docs issue here dotnet/docs#53347

Additional Context

dotnet/sdk#48795
dotnet/aspnetcore#65061
microsoft/azure-pipelines-tasks#22040