Skip to main content

.NET Core - Remove older SDKs and runtimes

Last week I talked about a bug we discovered in the latest(at the moment of writing) .NET core runtimes that caused our Razor ViewComponents no longer being rendered.

We found a workaround by explicitly setting the SDK version using a global.json file:

The global.json file above selects 6.0.300 or any later feature band or patch for 6.0 that is installed on the machine. Although this is a good workaround we wanted to avoid to have all developers update their projects.

So on the build server we tried a different approach. Our first attempt was rolling back the Visual Studio build tools but that didn’t turn out to be a good solution.

Luckily we can also uninstall a .NET Core SDK version using the .NET Uninstall Tool (dotnet-core-uninstall) . This tool is not installed out-of-the-box so you first need to download it here. After downloading it, run the MSI to install it.

Running the tool

Now that we have the uninstall tool installed, we can execute it.

First run the dotnet-core-uninstall list command to see the list of installed .NET SDKs and runtimes that can be removed with this tool.

As you can see in the screenshot above, some SDKs and runtimes are required by Visual Studio and they're displayed with a note of why it isn't recommended to uninstall them.

Now we can do a dry run to see what will happen when we do an uninstal by using the dry-run or whatif command:

If everything looks good you can finally do a real delete using the remove command:

Remark: Make sure you are running your commandline with administrator privileges.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more