You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/tools/dotnet-workload-sets.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ To "pin" the `install` command:
63
63
dotnet workload install maui-ios
64
64
```
65
65
66
-
This command installs the `maui-ios` workload using the workload version from the workloadset version `9.0.100-preview.7.24414.1`, since the preceding `install` command example pinned that workload set.
66
+
This command installs the `maui-ios` workload using the workload version from the workload-set version `9.0.100-preview.7.24414.1`, since the preceding `install` command example pinned that workload set.
67
67
68
68
Using `--version` with either `install` or `update` pins `install` to the specified version, but `update` is only configured for `workload-set` update mode, not to a specific workload-set version. If you then run `dotnet workload update` without the `--version` option, the `update` command:
69
69
@@ -97,7 +97,7 @@ To specify a workload-set version to update to when you're not specifying it in
97
97
dotnet workload update --version 8.0.400
98
98
```
99
99
100
-
`workload-set` update mode will be selected if it wasn't already selected.
100
+
`workload-set` update mode will be selected if it wasn't already selected.
101
101
102
102
## Use global.json for the workload-set version
103
103
@@ -115,7 +115,7 @@ To use a `global.json` file to specify the workload-set version for a repository
115
115
}
116
116
```
117
117
118
-
With the current directory in the same repository and the CLI in `workload-set` update mode, the `install`, `update`, and `restore` commands install workloads for the specified workload-set version. If you don't have a global.json file, and you're in `workload-set` update mode, the `restore` command installs the workload-set version that was established when you switched from manifests update mode to `workload-set` update mode.
118
+
With the current directory in the same repository and the CLI in `workload-set` update mode, the `install`, `update`, and `restore` commands install workloads for the specified workload-set version. If you don't have a global.json file and you're in `workload-set` update mode, the `restore` command installs the workload-set version that was established when you switched from manifests update mode to `workload-set` update mode.
119
119
<!--If you're using SDK 9, you defaulted to `workload-set` update mode, and you might not have established a workload-set version. In that case, `restore` installs the latest workload set available on the configured feeds.-->
120
120
121
121
If you have a workload-set version in the global.json file, the workload commands are in `workload-set` mode even if you haven't run the `config` command or used `--version`. The global.json file overrides those.
@@ -127,7 +127,7 @@ In manifests update mode, `restore` installs or updates workloads to the latest
127
127
128
128
## Check the update mode and version
129
129
130
-
To see the current update mode, run the `config` command with the `--update-mode` option without an argument. The mode is either workload-set` or `manifests`. For example:
130
+
To see the current update mode, run the `config` command with the `--update-mode` option without an argument. The mode is either `workload-set` or `manifests`. For example:
131
131
132
132
```dotnetcli
133
133
dotnet workload config --update-mode
@@ -159,11 +159,11 @@ dotnet workload --version
159
159
160
160
## Choose a workload-set version
161
161
162
-
Workload sets are published to nuget.org with each release of the .NET SDK, under the package ID `Microsoft.NET.Workloads.<feature band>`. For a stable version of the SDK, we plan on always having a matching workload-set version. So 8.0.400 SDK can install an 8.0.400 workload set, 401 can install a 401 set. In general, we recommend that you install the matching workload set for a stable SDK.
162
+
Workload sets are published to nuget.org with each release of the .NET SDK, under the package ID `Microsoft.NET.Workloads.<feature band>`. For a stable version of the SDK, there is always a matching workload-set version. So 8.0.400 SDK can install an 8.0.400 workload set, and 401 can install a 401 set. In general, we recommend that you install the matching workload set for a stable SDK.
163
163
164
164
For preview releases, find the corresponding workload-set version in the package's README tab. For example, see [the README tab for the .NET 9 Preview 7 package](https://www.nuget.org/packages/Microsoft.NET.Workloads.9.0.100-preview.7/9.100.0-preview.7.24414.1#readme-body-tab).
165
165
166
-
This is a preview release. In the future we'll give you ways to list workload set versions to see what's available and what they contain.
166
+
In the future, you'll be able to see a list of workload-set versions and what they contain.
167
167
168
168
## Ignore workload sets
169
169
@@ -173,7 +173,7 @@ To install, or update to, the latest version of each individual workload availab
173
173
dotnet workload config --update-mode manifests
174
174
```
175
175
176
-
In .NET 8.0.4xx SDK, manifests mode is the default. You need to select manifests mode explicitly only if you earlier explicitly selected `workload-set` update mode.
176
+
In .NET 8.0.4xx SDK, manifests mode is the default. In this version, you need to select manifests mode explicitly only if you explicitly selected `workload-set` update mode previously.
0 commit comments