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

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more