Skip to content

rollForward = disable should mention that's recommended when using lock files #53347

@Frulfump

Description

@Frulfump

Type of issue

Typo

Description

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.

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

It will aid in discovery of this fact

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

Opened matching docs for NuGet here NuGet/Home#14867

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/global-json

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/global-json.md

Document Version Independent Id

6d80613f-42dc-35d7-aeff-3187a36dbbca

Platform Id

8e1f5348-e2c6-2d5e-9531-202d840f33ca

Article author

@meaghanlewis

Metadata

  • ID: a94c335b-0b65-96cc-1c25-65777fbe4bb5
  • PlatformId: 8e1f5348-e2c6-2d5e-9531-202d840f33ca
  • Service: dotnet-fundamentals

Related Issues


Associated WorkItem - 571740

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

Status

🔖 Ready

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions