Lock file docs should mention it's recommended to use `global.json` with `rollForward = disable` when using lock files
#14.867 aberto em 22 de abr. de 2026
Métricas do repositório
- Stars
- (1.459 stars)
- Métricas de merge de PR
- (Mesclagem média 464d 23h) (1 fundiu PR em 30d)
Description
Docs Page URL
Description of the Issue
See comment from Microsoft(Chet) here https://github.com/dotnet/sdk/issues/48795#issuecomment-3001803076
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 https://github.com/dotnet/aspnetcore/issues/64897 https://github.com/dotnet/sdk/issues/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 https://github.com/dotnet/docs/issues/53347
Additional Context
https://github.com/dotnet/sdk/issues/48795 https://github.com/dotnet/aspnetcore/issues/65061 https://github.com/microsoft/azure-pipelines-tasks/issues/22040