Microsoft has urged builders nonetheless utilizing the long-term assist (LTS) launch of .NET Core 3.1 emigrate to the newest .NET Core variations till it reaches the tip of assist (EOS) subsequent month.
The firm warned clients on the Windows message heart to improve to .NET 6 (LTS) or .NET 7 “as quickly as potential” earlier than .NET Core 3.1 (LTS) reaches EOS on December 13, 2022.
As Dominique Whittaker, the Senior Program Manager accountable for .NET Core and .NET Native releases, warned this July, Microsoft will cease offering technical assist or servicing updates after EOS.
“We advocate transferring to .NET 6 as quickly as potential. If you might be nonetheless utilizing .NET Core 3.1 after the tip of assist date, you’ll have to replace your app to .NET 6 or .NET 7 to stay supported and proceed to obtain .NET updates,” Whittaker stated.
While .NET Core 3.1 apps will nonetheless run after the EOS is reached in lower than a month, they are going to be uncovered to assaults concentrating on any of the safety vulnerabilities patched in .NET Core 6 since its preliminary launch in November 2021.
Whittaker additionally shared detailed steps on how software program distributors and builders can improve to .NET 6 (LTS) and how one can replace their growth setting.
“If you’re migrating an app to .NET 6, some breaking adjustments may have an effect on you. We advocate you to undergo the compatibility test,” the Microsoft PM added.
Those who wish to migrate to the newest out there launch can improve to .NET 7, which was launched earlier this month on November eighth and might be supported for 18 months.
“.NET 7 brings your apps elevated efficiency and new options for C# 11/F# 7, .NET MAUI, ASP.NET Core/Blazor, Web APIs, WinForms, WPF and extra,” the .NET workforce stated.
“With .NET 7, you can too simply containerize your .NET 7 tasks, arrange CI/CD workflows in GitHub actions, and obtain cloud-native observability.”
In April, Microsoft additionally warned builders emigrate their apps away from .NET Framework 4.5.2, 4.6, and 4.6.1 to at the very least .NET Framework 4.6.2 or later earlier than they reached their EOS on April 26, to proceed receiving safety updates and technical assist.
These three .NET Framework variations have been retired after the change to SHA-2 signing as a result of they have been digitally signed with certificates utilizing the legacy and insecure SHA-1 cryptographic hashing algorithm.