Skip to main content

Using the .NET Upgrade Assistant to upgrade a Windows Forms App–Part II

Yesterday I demonstrated how we could use the .NET Upgrade Assistant to help us port a 10 year old WinForms application to .NET Core. We tried the 'analyze' mode to do a dry-run of the upgrade process.

Today I continue with a follow-up post where we have a look at the warnings and diagnostic messages I got and see how we can get rid of them.

Warning - HighDpiMode

We’ll start easy with the following warning:

HighDpiMode needs to set in Main() instead of app.config or app.manifest - Application.SetHighDpiMode(HighDpiMode.<setting>). It is recommended to use SystemAware as the HighDpiMode option for better results.

As I’m not using the HighDpiMode in my application, I can just ignore this warning (see this related Github issue: If you need to set the HighDpiMode, have a look at the changed bootstrapping logic here:

Warning – Detected package downgrade

Let’s move on to the next warning:

[WRN] [NuGet] Detected package downgrade: System.ServiceModel.Security from 4.9.0 to 4.8.1. Reference the package directly from the project to select a different version. project -> Microsoft.Windows.Compatibility 6.0.0 -> System.ServiceModel.Security (>= 4.9.0) project -> System.ServiceModel.Security (>= 4.8.1)

These warnings are caused by the Microsoft.Windows.Compability NuGet package. This package will introduce a reference to a lot of other packages(with some System.ServiceModel related dependencies as a part of them).

The original application was using the 4.8.1 versions of those packages. Upgrading to 4.9.0 should not be a problem. This means that this warning will disappear once all projects in the solution are upgraded.

Another one that we can safely ignore. Nice!

Diagnostic UA0002

Another log line that triggered my attention was the following:

Diagnostic UA0002 with the message This type is not supported on .NET Core/.NET 5+ and should be replaced with a modern equivalent’

I had a look at the Analysis.sarif file that was generated as part of the analyze process. Unfortunately that didn’t gave any extra clue on what this message was referring to.

There is an open Github issue related to this:

So we had to skip this message as I didn’t know what to do.

Diagnostic UA0013_I

The last log message I want to have a look at is the following one:

Diagnostic UA0013_I with the message Windows Forms Deprecated controls : Microsoft.Reporting.WinForms.ReportViewer is no longer supported’

Microsoft provided a solution in the form of an updated ReportViewer WinForms control that can be downloaded from the Visual Studio Marketplace here:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should

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.