Skip to main content

.NET Upgrade Assistant now supports upgrading to Centralized Package Management

Centralized package management in Visual Studio is a feature that allows you to manage NuGet package dependencies for multiple projects from a single location. This is particularly useful for large solutions with many projects, as it simplifies the process of keeping package versions consistent across the entire solution.

To enable centralized package management, you need to create a Directory.Packages.props file at the root of your repository and set the MSBuild property ManagePackageVersionsCentrally to true. Inside this file, you define the package versions required by your projects using <PackageVersion /> elements. For each project, you then define a <PackageReference /> but omit the Version attribute, as the version will be obtained from the corresponding <PackageVersion /> item.

Although this is not that much work, if you find this still too cumbersome I have some good news for you; with the latest release of the .NET Upgrade Assistant, you can let the assistant do the migration for you.

Let’s give it a try…

First make sure that the .NET Upgrade Assistant extension is installed in your Visual Studio instance:

  • Open Visual Studio. Go to the Extensions > Manage Extensions menu to open the Extension Manager window.

  • Select the Browse tab.

  • Type .NET upgrade assistant into the search box.

  • Select the .NET Upgrade Assistant item, and then select Install.

Once you have the .NET Upgrade Assistant available inside Visual Studio, we can start the upgrade:

  • Right click on a project in your Solution Explorer and click on Upgrade.
    • Remark: You have to click on a specific project and NOT on the solution file, otherwise you get a different screen

 

  • Now you get a welcome screen where you can choose the NuGet central package management option.

 

  • As a next step we get a list of all the projects in our solution. Click Next to continue.

 

  • Now we can customize the upgrade process if we want to. The defaults are fine so let’s click Upgrade to start the upgrade process.

 

  • We can monitor the upgrade process on the next screen. That’s it!

More information

NuGet Central Package Management

Central Package Management - warning NU1507: There are 2 package sources defined in your configuration.

.NET Upgrade Assistant Now Supports Upgrading to Centralized Package Mangement - .NET Blog

Install .NET Upgrade Assistant - .NET Core | Microsoft Learn

Central Package Management | Microsoft Learn

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