Bulk Updating .NET Framework Versions In Legacy Projects With Powershell

For one of our customers, I recently had to change the target .NET Framework version from 4.5.1 to 4.6.1 because a new version of some important Nuget package requires .NET 4.6.1. Changing the framework version in newer SDK-based projects is not a problem but the old csproj files, the big ones with the packages.config file, need some special treatment.

In this article:

Pawel Gerr is architect consultant at Thinktecture. He focuses on backends with .NET Core and knows Entity Framework inside out.

The required steps are:

  1. Update the TargetFrameworkVersion to v4.6.1 in all csproj files.
  2. Use the Package Manager Console in Visual Studio to re-install the Nuget packages without increasing the version of installed packages. This Package Manager Console is a special one providing us with some PowerShell commands that are not available otherwise. We need to re-install the Nuget packages because it…

    • updates the target framework version in the packages.config
    • adjusts the (package) reference in case the Nuget package has different DLLs for different .NET versions
    • runs PowerShell scripts if the Nuget package has any
    • updates the assembly bindings in app.config / web.config

You can work on these tasks manually if you are only dealing with a dozen projects and a few solutions files, but it is not practical with 40 solutions containing over 300 projects. Furthermore, there might be plans to test the applications with higher .NET versions, like 4.7.2, in that case, we might have to do all the steps multiple times.

Update the TargetFrameworkVersion

I am using a PowerShell script to find all project files (*.csproj) and update the TargetFrameworkVersion.

First, we need to find all project files starting from the repository root (e.g. C:\Projects\MyLegacyProject).

					using namespace System.Collections.Generic # for List<T> 

$dir = "." # points to "repository root"
$targetFrameworkVersion = [Version]::new("4.6.1")

$projFiles = Get-ChildItem $dir -Recurse -Filter *.csproj


Next, we fetch the content of each project file and extract the current framework version. All the information is saved in a custom object.

					$projsWithVersion = [List[object]]::new()

foreach($file in $projFiles)
    $content = [xml](Get-Content $file.FullName)
    $versionNodes = $content.GetElementsByTagName("TargetFrameworkVersion");
        0 {
            Write-Host "The project has no framework version: $file.FullName"
        1 {
            $version = $versionNodes[0].InnerText;

                File = $file;
                XmlContent = $content;
                VersionNode = $versionNodes[0];
                VersionRaw = $version;
                Version = [Version]::new($version.Replace("v", ""))
        default {
            Write-Host "The project has multiple elements of TargetFrameworkVersion: $file.FullName"

If you want to know how many projects are referencing what version then you can call the following function.

					function Print-Version-Statistics([List[object]] $projsWithVersion)
    $numberOfProjectsByVersion = @{}

    foreach($proj in $projsWithVersion)
            $numberOfProjectsByVersion[$proj.Version] = $numberOfProjectsByVersion[$proj.Version] + 1
            $numberOfProjectsByVersion[$proj.Version] = 1
    Write-Host "`nCurrent version distribution:"

The next PowerShell fragment is updating the TargetFrameworkVersion if the current version is less than 4.6.1.

					foreach($proj in $projsWithVersion)
    if($targetFrameworkVersion.CompareTo($proj.Version) -gt 0)

Re-install all Nuget Packages

After the execution of the script all csproj files are targeting .NET 4.6.1. Lastly you need to run the command Update-Package -reinstall in the Package Manager Console in Visual Studio but there is an issue. I neither have a solution referencing all projects, nor do I want to open 40 solutions. Let’s extend our previous PowerShell script so it creates a new solution with all projects in it.For that, we will use the dotnet (core) CLI.

					$slnName = "AllProjects" # name without file extension
$slnFilePath = Join-Path $dir ($slnName + ".sln")

dotnet new sln -o $dir -n $slnName # creates new sln-file

foreach($proj in $projsWithVersion)
    # adds the project to solution
    # filter out unchanged projects if needed
    dotnet sln $slnFilePath add $proj.File.FullName

But before executing the script, we need to do something. Otherwise, dotnet CLI will raise an error because of missing MsBuild tasks. Usually, the old projects are referencing some Visual-Studio-specific MsBuild tasks that do not come with the .NET Core SDK.

On my machine, I have Visual Studio 2019 installed, so the MsBuild tasks are in folder C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio. Currently, my .NET Core SDK is 3.1.200 so the CLI is searching for MsBuild tasks in C:\Program Files\dotnet\sdk\3.1.200\Microsoft\VisualStudio which does not exist. If you are using a different version of Visual Studio or SDK then you have to adjust the folder paths accordingly.
To make the CLI happy, we have to copy the whole folder C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio to C:\Program Files\dotnet\sdk\3.1.200\Microsoft. Alternatively, instead of copying the folder, you can create a symbolic link.

After letting the script run, we should have a new AllProjects.sln. What you still need to do is to open the solution in Visual Studio and execute Update-Package -reinstall in the Package Manager Console. Depending on the number of projects it could take several minutes to complete.


After working with SDK-based projects, the older projects feel quite inconvenient. The amount of work I showed you in this article is actually not necessary with newer projects. In that case, you neither need PowerShell nor Visual Studio to update a version, a Directory.Build.props/Directory.Build.targets files usually are more than enough to apply changes to multiple projects.


Current articles, screencasts and interviews by our experts

Don’t miss any content on Angular, .NET Core, Blazor, Azure, and Kubernetes and sign up for our free monthly dev newsletter.

EN Newsletter Anmeldung (#7)
Related Articles
One of the more pragmatic ways to get going on the current AI hype, and to get some value out of it, is by leveraging semantic search. This is, in itself, a relatively simple concept: You have a bunch of documents and want to find the correct one based on a given query. The semantic part now allows you to find the correct document based on the meaning of its contents, in contrast to simply finding words or parts of words in it like we usually do with lexical search. In our last projects, we gathered some experience with search bots, and with this article, I'd love to share our insights with you.
If you previously wanted to integrate view transitions into your Angular application, this was only possible in a very cumbersome way that needed a lot of detailed knowledge about Angular internals. Now, Angular 17 introduced a feature to integrate the View Transition API with the router. In this two-part series, we will look at how to leverage the feature for route transitions and how we could use it for single-page animations.
.NET 8 brings Native AOT to ASP.NET Core, but many frameworks and libraries rely on unbound reflection internally and thus cannot support this scenario yet. This is true for ORMs, too: EF Core and Dapper will only bring full support for Native AOT in later releases. In this post, we will implement a database access layer with Sessions using the Humble Object pattern to get a similar developer experience. We will use Npgsql as a plain ADO.NET provider targeting PostgreSQL.