dotnet workload clean

ByMarius Bughiu
1 Comment

Note: this command is only available starting with .NET 8.

This command cleans up workload packs that might be left over after an .NET SDK or Visual Studio update. It can be useful when encountering issues while managing workloads.

dotnet workload clean will clean up orphaned packs resulted from uninstalling .NET SDKs. The command will not touch workloads installed by Visual Studio, but it will provide you with a list of workloads that you should clean-up by hand.

dotnet workloads can be found at: {DOTNET ROOT}/metadata/workloads/installedpacks/v1/{pack-id}/{pack-version}/. An {sdk-band} file under the installation record folder will keep a reference count – so that when there’s no sdk-band file under a worload folder, then we know that the workload package is not in use and can be safely deleted from the disk,

dotnet workload clean –all

While in it’s default configuration the command removed only orphaned workloads, by passing the --all argument, we are instructing it to clean up every pack on the machine – except for those installed by Visual Studio. It will also remove all workload instalation records.

Similar Posts

|

How to publish container as tar.gz in .NET

ByMarius Bughiu

Starting with .NET 8, it’s possible to directly generate a tar.gz container archive. This is particularly advantageous for more complex workflows where activities like scanning the images before pushing them are needed. After creating the archive, it can be transferred, scanned, or incorporated into your local Docker setup. For archiving during publication, integrate the ContainerArchiveOutputPath…

|

Implementation type Data.AppDbContext can’t be converted to service type Microsoft.AspNetCore.Identity.IUserStore

ByMarius Bughiu

This exception is thrown when you are building an identity DbContext without providing the user and role stores using AddUserStore and AddRoleStore. You can provide both configurations with a single call to AddEntityFrameworkStores like in the example below: The full exception for reference: System.AggregateException: ‘Some services are not able to be constructed (Error while validating…

.NET 8 Performance: UnsafeAccessor vs. Reflection
| |

.NET 8 Performance: UnsafeAccessor vs. Reflection

ByMarius Bughiu

In a previous article we covered how to access private members using UnsafeAccessor. This time around, we want to look at it’s performance compared to Reflection, and to see whether it’s truly zero-overhead or not. We’re going to do four benchmarks. If you want to run the benchmarks yourself, you have the code below: Benchmark…

| |

NET 8 – How to use JsonStringEnumConverter with native AOT

ByMarius Bughiu

JsonStringEnumConverter is not compatible with native AOT. To fix that, NET 8 introduces a new converter type JsonStringEnumConverter<TEnum> that is compatible with native AOT. To use the new type, simply annotate your types as follows: Keep in mind: enum deserialization is case insensitive, while serialization can be cusomized via JsonNamingPolicy. What happens if you try…

One Comment

  1. Pingback: What's new in .NET 8 - Start Debugging

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you a human? *