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.

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

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.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should