Visual ReCode 1.2 is out with beta support for migrating various .NET 4.x projects to .NET Core 3.1. To try out this new feature, Download Visual ReCode now!
Migrate WPF and Windows Forms apps to .NET Core 3.1
There are various .NET project types that can be migrated to .NET Core 3.1 with very few changes: WPF and Windows Forms are both supported in Core (although apps can still only run on Windows), and of course console apps, class libraries and so on can be converted too. Of course, you need to move all the code and everything else to the new SDK project format, and that’s where we can help.
Visual ReCode now has a wizard-driven process for migrating .NET 4.x projects,
whether using the old project format or the new SDK format but still targeting
net4xx framework, to a shiny new .NET Core 3.1 solution.
NuGet Package Updates
If your project references NuGet packages, ReCode will check to see if they are compatible with .NET Core. If they’re not, it will look for a later version that is compatible. For example, if your app uses Newtonsoft.Json 8.0, ReCode will update it to the latest 12.0 version.
ReCode will also add new NuGet packages for things that used to be local framework
remove any packages that are no longer necessary, like
System.Threading.Tasks.Extensions, which are
built-in to the .NET Core SDK.
If you’re building desktop .NET applications, we know you’re probably using one of the many excellent third-party component collections from people like DevExpress, Telerik and Syncfusion. Most of them have already announced .NET Core 3.1 support, and we’re hoping to provide a way to update those references too, even from on-disk assembly references to NuGet package references.
Supported Project Types
This first release includes support for:
- WPF applications and libraries
- Windows Forms applications and libraries
- Plain class libraries
- Console applications
We hope to follow this soon with a second beta which will also support:
- xUnit, NUnit and MSTest projects
- Windows Service projects (to convert to .NET Core Worker projects)
We’re also planning to add support for migrating to the .NET 5 preview in that release, so you can test your apps with the very latest bits out of Redmond.
As with our WCF to gRPC migration, each .NET Project migration produces a report highlighting possible issues with the new application, including NuGet packages where ReCode couldn’t find a .NET Core-compatible version, on-disk assembly references that are probably .NET 4.x, and so on.
It’s a beta
This is a preview release, and it’s been testing on a limited number of apps (including ICSharpCode.TextEditor!), so we’re hoping you’ll download Visual ReCode and try it on your projects. Let us know how you get on!