Before any migration starts, you’ll want to know which are your problematic libraries. Some of it, however, isn’t and will work only on Windows. Most of the codebase is platform-agnostic and will work in any operating system. NET Core/.NET Standard.Ī lot of migration processes will depend not just on your solution, but also on how your software is developed and released. Code migration: convert your C# code to.csprojs files: convert your project files to the mandatory format. Understand where each project fits in the migration strategy, depending on its complexity and amount of Windows-specific code. Migration types: choose how to migrate based on how your software is developed and released.Code analysis: learn how compatible your solution is with.We’ve gone through the process, and we can split it into four main considerations. To help out anyone who might be going through the same, we decided to share things that have worked for us, as well as some lessons learned.NET Core Migration Recommendations

NET 5 full-version would be arriving at the end of 2020, so we’d decided to start preparing our projects for what’s coming. NET 5 (jumping over “version 4” only as a cosmetic change and dropping “Core” for simplicity’s sake, since there won’t be a “Framework” anymore). NET Core 3.x, the next major release would be.

Checking .net version