dotnet-workload-restore(1)

📦
version 11.0.0~rc3 · 6 versions
, in alpine 3.24, centos-stream 10, centos-stream 9, fedora 43, fedora 44, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 dotnet-workload-restore — the manual page, but make it cute 💖

okay bestie, welcome to the dotnet-workload-restore(1) manual page ✨ it lives in the .NET Documentation section of the manual, and it's giving "let me install exactly what your project needs and nothing else" 💅

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

🌸 NAME 🌸

dotnet-workload-restore — installs workloads needed for a project or a solution. literally it just gets you set up, no drama 💖

✨ SYNOPSIS ✨

dotnet workload restore [<PROJECT | SOLUTION>]
    [--configfile <FILE>] [--disable-parallel]
    [--ignore-failed-sources] [--include-previews] [--interactive]
    [--no-cache] [--skip-manifest-update] [-s|--source <SOURCE>]
    [--temp-dir <PATH>] [-v|--verbosity <LEVEL>] [--version <VERSION>]

dotnet workload restore -?|-h|--help

the first one is the "do the thing" form, the second one is the "bestie explain the thing" form 🦋

🎀 DESCRIPTION 🎀

So. The dotnet workload restore command looks at a project or a solution, figures out which workloads it needs, and then installs any workloads that are missing. it's like a vibe check for your dependencies, but it actually fixes them ✨

For more information about the dotnet workload commands, see the dotnet workload install command. iykyk, they're cousins 👑

🦋 ARGUMENTS 🦋

  • PROJECT | SOLUTION — the project or solution file to install workloads for. If a file is not specified, the command searches the current directory for one. so if you're lazy (valid), it just sniffs around where you're standing 🙈

💅 OPTIONS 💅

  • --configfile <FILE> — the NuGet configuration file (nuget.config) to use. If specified, only the settings from this file will be used. If not specified, the hierarchy of configuration files from the current directory will be used. For more information, see Common NuGet Configurations. one file only, no blending, she's monogamous 💖
  • --disable-parallel — prevents restoring multiple projects in parallel. one at a time, single file line, main character energy 🎀
  • -?|-h|--help — prints out a description of how to use the command. the "help me help you" flag 🫶
  • --ignore-failed-sources — treats package source failures as warnings. oh that source flopped? cute, we move on 💀
  • --include-previews — allows prerelease workload manifests. living on the edge, respect 🔥
  • --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 "bestie, type your password" 😭
  • --no-cache — prevents caching of packages and http requests. no hoarding, fresh every time ✨
  • --skip-manifest-update — skip updating the workload manifests. The workload manifests define what assets and versions need to be installed for each workload. fyi the manifests are the little blueprint of what assets and versions go with each workload 🧚
  • -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. Multiple sources can be provided by specifying this option multiple times. she overrides EVERYTHING in the config files, no cap 👑
  • --temp-dir <PATH> — specify the temporary directory used to download and extract NuGet packages (must be secure). must be secure, fr fr, don't put this 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. For more information, see <xref:Microsoft.Build.Framework.LoggerVerbosity>. the brackets mean you can just type the short letter, iconique 🌈
  • --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. so if global.json already claimed the version, she's not gonna let you double-dip — step outside that path and then you can 💅

🌟 Example 🌟

  • Restore workloads needed by MyApp.csproj:
dotnet workload restore MyApp.csproj

that's it. that's the whole thing. ate and left no crumbs 🍓

okay that's the whole page bestie, you're officially a workload-restore girlie now 💖

this page is dated 2025-06-13 and it's page dotnet-workload-restore(1) of the manual — mwah, see you in the next one, take care of yourself 🎀🦋✨

📦 where this page comes from