dotnet-workload-repair(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-repair(1) πŸ’–

okay bestie, welcome to the dotnet-workload-repair page, straight out of the .NET Documentation set πŸŽ€ this one's for the .NET girlies on .NET 6 SDK and later versions ✨ (yes, βœ”οΈ that's a checkmark, we love a supported version)


🌸 NAME 🌸

dotnet-workload-repair β€” literally repairs your workload installations. that's it. that's the job. πŸ› οΈπŸ’…


✨ SYNOPSIS ✨

dotnet workload repair
    [--configfile] [--disable-parallel] [--ignore-failed-sources]
    [--interactive] [--no-cache]
    [-s|--source <SOURCE>] [--temp-dir <PATH>]
    [-v|--verbosity <LEVEL>]

dotnet workload repair -?|-h|--help

πŸ¦‹ DESCRIPTION πŸ¦‹

so dotnet workload repair reinstalls all installed workloads. no cap. πŸ”

here's the tea though: workloads are made up of multiple workload packs, and it's absolutely possible to end up in a cursed half-installed state where some packs installed successfully and others just… didn't. 😭 classic. for example, a dotnet workload install command might not finish installing because your internet connection dropped mid-download. been there. it's giving ✨chaos✨.

want more info about the dotnet workload commands in general? go peek at the dotnet workload install command. πŸ“š


πŸ‘‘ OPTIONS πŸ‘‘

  • --configfile <FILE> β€” the NuGet configuration file (nuget.config) you want to use. if you specify it, only the settings from this file get used. if you don't specify it, it walks the hierarchy of configuration files starting from the current directory. more deets in Common NuGet Configurations. πŸ“„
  • --disable-parallel β€” stops it from restoring multiple projects in parallel. one at a time, bestie. πŸšΆβ™€οΈ
  • -?, -h, --help β€” prints out a description of how to use the command. the little "help me" button. πŸ†˜
  • --ignore-failed-sources β€” treats package source failures as warnings instead of, y'know, a whole thing. πŸ™ˆ
  • --include-previews β€” allows prerelease workload manifests. living on the edge, I respect it. πŸ”₯
  • --interactive β€” lets the command stop and wait for you to do something, like type or complete authentication. it's waiting on you, main character. πŸ’œ
  • --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. and yes, you can provide multiple sources by specifying this option multiple times. stack 'em. 🧚
  • --temp-dir <PATH> β€” specify the temporary directory used to download and extract NuGet packages. must be secure. πŸ”’ don't play with this one.
  • -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>. πŸ—£οΈ

🌈 EXAMPLES 🌈

  1. Repair all installed workloads:
dotnet workload repair

that's the whole vibe. run it, let it cook, and all your packs get reinstalled. slay. πŸ’–


quick reminder bestie: this page is dotnet-workload-repair(1) from .NET Documentation, dated 2025-06-13 πŸŽ€ keep it around, it's iconic. bye pookie, go repair those workloads πŸ’…βœ¨πŸ«Ά
πŸ“¦ where this page comes from