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

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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more