Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In .NET 10 Preview 2, the default workload update mode changed from "manifests" to "workload-set". This change ensures users use a single, coherent set of workload versions that do not individually float, making it easier to maintain consistency and manage workloads.
Version introduced
.NET 10 Preview 2
Previous behavior
Previously, workloads operated in 'loose manifest' mode by default. Errant dotnet workload update commands could install new versions that might not work well together, making it difficult for users to keep a consistent set of workload versions aligned.
New behavior
Workloads will never float unless you:
- Update your SDK.
- Perform an explicit update command.
When you perform an update, all workloads will use known-matching versions from the workload set that is used.
Type of breaking change
This is a behavioral change.
Reason for change
Users requested more control and predictability in workload management. This new system allows for pinning and coherent updates, ensuring a consistent set of workload versions.
Recommended action
No corrective action is necessary. If you experience issues, you can revert to loose manifest mode by running the following command:
dotnet workload config --update-mode manifests
Affected APIs
None.
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
