Skip to main content

Convert a project to use centralised package management

If you have never heard about Central Package Management(CPM), first have a look at my blog post a few months ago. Done reading? Ok, we continue...

To summarize, with CPM you bring all your dependencies in one place (the Directory.Packages.props file). This makes it easier to manage your dependencies for a large multiproject solution and helps you to avoid version drift where multiple versions of the same package are used inside your solution.

Remark: CPM works both in Visual Studio and in JetBrains Rider.

Convert your .NET solution to CPM manually

If you want to start using CPM for your existing solutions, there are a few steps you need to repeat for every project inside your solution:

  • Go through all of the csproj files and copy the references into the centralised Directory.Packages.props file
  • Remove all the versions from the package reference entries in the csproj files.

Although not that hard to do, it would be nice if this can be done automatically.

Automate the process with CentralisedPackageConverter

I was wondering if I would try to create my own tool to automate this. Luckily someone else already did this.

Let me introduce the CentralisedPackageConverter global tool.

First install the tool using:

dotnet tool install CentralisedPackageConverter –global

Now we can run the tool using:

central-pkg-converter <folder path>

The tool will ask for confirmation. Hit 'y' to continue.

If you want to check what the impact of running the tool will be, you can run it in ‘dry mode’ using –d

central-pkg-converter <folder path> –d

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

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more