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.
Note
dotnetup is in public preview. Its features and behavior might change before general availability.
dotnetup uses global.json to associate an SDK requirement with a
repository or directory tree. It searches from the current directory through
each parent directory and reads the nearest existing global.json.
Install from global.json
Run an SDK install command without a channel:
dotnetup install
If the nearest global.json has an sdk.version, dotnetup derives an
install specification from the version and rollForward value. It records
the full path to the file as the specification source. If no
global.json exists in the current directory or its parent directories, the
command uses the latest channel. If the nearest file is malformed or
contains comments, parsing fails. dotnetup does not skip that file to search
parent directories or use the latest channel.
rollForward mapping
dotnetup maps global.json SDK selection policies to updateable channels:
rollForward value |
Stored dotnetup requirement for SDK 10.0.103 |
|---|---|
Omitted or latestPatch |
10.0.1xx |
latestFeature |
10.0 |
latestMinor |
10 |
latestMajor |
latest |
disable, patch, feature, minor, or major |
10.0.103 |
The exact-version mappings are pinned and are not advanced by an update.
The allowPrerelease property does not affect the channel that dotnetup derives.
Installation path from global.json
If sdk.paths contains an entry, dotnetup uses the first path. A relative
path is resolved from the directory that contains global.json.
In the current public-preview build, dotnetup treats the first entry as a
path. It doesn't interpret $host$ as a sentinel or skip empty entries.
Installation-path precedence is:
--install-path.- The first
sdk.pathsentry in the nearestglobal.json. - The default dotnetup-managed .NET installation root.
Keep repository files current
Pass --update-global-json to replace sdk.version with the concrete SDK
version that was installed or updated:
dotnetup install --update-global-json
dotnetup sdk update --update-global-json
Only global.json-sourced SDK specifications are updated by the update workflow. The modifier preserves the other JSON properties, formatting, and detected text encoding.
Remove matching repository requirements
A tracked global.json specification is refreshed during garbage collection.
If the file no longer exists or no longer contains an SDK version, the
specification is removed.
To remove specifications by channel, select the globaljson source. This
command removes every matching specification in the selected installation
root, not only one repository:
dotnetup sdk uninstall 10.0.1xx --source globaljson
Use dotnetup list to find the stored channel, source path, and installation
root. Add --install-path to select a custom root.
See also
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.
