Porting from .NET Framework to Modern .NET
Learn about considerations for porting .NET Framework applications to modern .NET, including suitable application types and potential benefits.
If we are an existing .NET Framework developer, we may have existing applications we think we should port to modern .NET. But we should carefully consider if porting is the right choice for our code because sometimes, the best choice is not to port.
For example, we might have a complex website project that runs on .NET Framework 4.8 but is only visited by a few users. If it works and handles the visitor traffic on minimal hardware, potentially spending months porting it to a modern .NET platform could be a waste of time. But if the website currently requires many expensive Windows servers, then the cost of porting could eventually pay off if we can migrate to fewer, less costly Linux servers.
The possibility of port
Modern .NET has great support for the following types of applications on Windows, macOS, and Linux, so they are good candidates for porting:
ASP.NET Core websites, including Razor Pages and MVC
ASP.NET Core web services (REST/HTTP), including Web APIs, Minimal APIs, and OData
ASP.NET Core-hosted services, including gRPC, GraphQL, and SignalR
Console App command-line interfaces
Modern .NET has decent support for the following types of applications on Windows, so they are potential candidates for porting: