dotnet-workload-update(1)

💖 dotnet-workload-update(1) — the .NET Documentation glow-up 💖

okay bestie, grab your iced coffee because we're talking about dotnet workload update, and it's literally the "spring cleaning but make it ✨automatic✨" of your SDK. this page lives in the .NET Documentation manual, and it's giving handy reference energy, fr fr.

This article applies to: ✔️ .NET 6 SDK and later versions

---

🌸 NAME 🌸

dotnet-workload-update — updates installed workloads. that's it, that's the whole vibe. 💅

---

✨ SYNOPSIS ✨

dotnet workload update
    [--advertising-manifests-only]
    [--configfile <FILE>] [--disable-parallel]
    [--from-previous-sdk] [--ignore-failed-sources]
    [--include-previews] [--interactive] [--no-cache]
    [-s|--source <SOURCE>] [--temp-dir <PATH>]
    [-v|--verbosity <LEVEL>] [--version]

dotnet workload update -?|-h|--help

---

🦋 DESCRIPTION 🦋

so the dotnet workload update command updates all installed workloads to the newest available versions. it hits up NuGet.org and asks for updated workload manifests like "hey bestie, what's new 👀". then it updates your local manifests, downloads the new versions of the installed workloads, and — this is the icon behaviour — removes all the old versions of each workload. no hoarding, we love a clean closet. 🎀

when the command is in workload-set update mode, workloads get updated according to the workload-set version, not the latest version of each individual workload. so it's like the whole squad moves together instead of everyone doing their own thing. for more info, see .NET SDK workload sets. workload-set mode is available since 8.0.400 SDK. (yes, that specific, we don't round up here 💅)

for more information about the dotnet workload commands, see the dotnet workload install command.

---

👑 OPTIONS 👑

• --advertising-manifests-only — downloads the advertising manifests, but doesn't actually update any workloads. it's giving "window shopping, no checkout". 🛍️
• --configfile <FILE> — the NuGet configuration file (nuget.config) to use. if you specify it, only the settings from this file get used, periodt. if you don't specify it, the hierarchy of configuration files starting from the current directory gets used instead. for more info, see Common NuGet Configurations.
• --disable-parallel — prevents restoring multiple projects in parallel. one at a time, no chaos, very demure. 🙈
• --from-previous-sdk — include workloads that were installed with previous SDK versions in the update. old SDK energy is still invited to the party. 🎉
• -? | -h | --help — prints out a description of how to use the command. the classic "help me help you". 💖
• --ignore-failed-sources — treats package source failures as warnings. she's forgiving like that. 🫶
• --include-previews — allows prerelease workload manifests. living on the edge, lowkey iconic. 🔥
• --interactive — allows the command to stop and wait for user input or action. for example, to complete authentication. it'll literally pause and be like "girl, I need you". 😭
• --no-cache — prevents caching of packages and http requests. fresh every time, no leftovers. ⭐
• -s | --source <SOURCE> — specifies the URI of the NuGet package source to use. this setting overrides all of the sources specified in the nuget.config files, so be aware. multiple sources can be provided by specifying this option multiple times. stack 'em up. 🧚
• --temp-dir <PATH> — specify the temporary directory used to download and extract NuGet packages (must be secure). key word: secure. don't put it somewhere cursed. 🔐
• -v | --verbosity <LEVEL> — sets the verbosity level of the command. allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]. the default is minimal. if you specify detailed or diagnostic verbosity, the command displays information about the NuGet packages that it downloads. basically it starts telling you everything and honestly? we love a chatty queen. 🗣️
• --version — the workload set version to install or update to. if you specify the workload-set version in global.json, you can't use the --version option to specify the workload-set version. to make it possible to use the --version option in that case, run the command outside of the path containing the global.json file. available since 8.0.400 SDK. for more information, see .NET SDK workload sets. (yes this one has rules, read them twice bestie 🙈)

---

🌈 EXAMPLES 🌈

1. update the installed workloads to the latest version of each individual workload:

dotnet workload config --update-mode manifests
dotnet workload update

2. update the installed workloads to the latest workload set version:

dotnet workload config --update-mode workload-set
dotnet workload update

---

and that's the whole page, bestie!! you ate this. 🍓✨

sending you off with the official receipts: this page comes from .NET Documentation and it's dated 2025-06-13, filed under dotnet-workload-update(1) — iykyk 💜