Grids, Hubs, & Buses... Oh My!

on

Preparing for the demise of .Net Framework

on
The .NET Framework, developed by Microsoft in the early 2000(s) and was originally called Next Generation Windows Services (NGWS). We have been using the .Net Framework for the last 20 years to build and run windows applications.   

Microsoft has been transitioning .Net Core and started this transition in 2014 with the initial release of .Net Core as a cross-platform, lightweight and open-source implementation of .Net.   Today, we are standing with .Net Core version 6.

 .NET Framework is gradually being phased out. The latest version of the .NET Framework, is .NET Framework 4.8.  Existing applications and frameworks will continue to be supported with bug fixes and security updates and there are plenty .Net Framework applications and services to be supported across the IT landscape.

Overall, the demise of the .NET Framework is a gradual process, and developers are encouraged to adopt the newer .NET Core and .NET 5+ frameworks for future application development.   But... When is the right time to address the migration to .Net Core?

Here are some items we consider during a migration:

  • How compatible is your application or dependencies with .Net Core
  • Time and resources required for migration
  • Current support and lifetime of existing framework
  • Does your application require cross-platform capability
    • (example) - Moving to cloud and you want to use Linux instead of Windows for cost considerations
  • Containerization options
  • New features in .Net Core
Ultimately, the decision to migrate should be based on a careful assessment of your specific application and its requirements. It's recommended to perform a pilot migration or proof of concept to evaluate the feasibility and benefits before committing to a full-scale migration. Future Systems is specializes with application architectures and migrations to .Net Core or to the cloud.