Skip to main content

.NET Core - View outdated packages

When creating and maintaining (.NET Core) applications, it is always a good idea to keep the dependencies up-to-date. This helps to fix identified vulnerabilities but also keeps the upgrade path short as you closely stay to the latest package version. In this post I show you 3 ways to identify outdated packages and update them when necessary.

Through the Visual Studio Package Manager

When using Visual Studio, it is easy to find out whether newer versions of the NuGet packages used by your project is available, by using the NuGet Package Manager:

  • Open your solution/project in Visual Studio
  • Go to Tools-> NuGet Package Manager –> Manage NuGet Packages for Solution…
  • Go to the Updates tab, check the Select all packages checkbox and click on Update

Through the dotnet-outdated global tool

A second option is to use the open source global .NET tool: dotnet-outdated.

  • First install the tool using the following command:
dotnet tool install --global dotnet-outdated-tool
  • Now you can call the tool using the following command:
dotnet-outdated
  • To update the  outdated packages run this command:
dotnet-outdated --upgrade

Through the .NET Core CLI

A last option is to use the .NET Core CLI directly.

  • To get the list of outdated packages, run the following command:
dotnet list package --outdated
  • Now if we want to update an outdated package, you can do the following:
dotnet add package PACKAGENAME

Remark: We have to repeat this command for every package that requires an update.

More information

dotnet list package command - .NET CLI | Microsoft Learn

GitHub - dotnet-outdated/dotnet-outdated: A .NET Core global tool to display and update outdated NuGet packages in a project

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.