End of Extended Support for Some .NET Framework, SQL Server Versions -- Visual Studio Magazine

End of Extended Support for Some .NET Framework, SQL Server Versions

Security risks will be a major concern for companies using some versions of .NET Framework and SQL Server after extended support ends some time this year.

By Kurt Mackie
01/04/2016

Microsoft will be ending extended support for some versions of .NET Framework this month and SQL Server in April, and that introduces security risks for companies who don't upgrade.

The end of extended support means Microsoft will stop issuing security patches or future hotfixes. Microsoft's enterprise software lifecycle product support is a policy with two five-year support phases, namely "mainstream support" and "extended support." At the end of those 10 years, Microsoft essentially considers its software to be "unsupported" and no longer developed.

Microsoft has specified a Jan. 12, 2016 end of extended support deadline for some .NET Framework 4 versions. After that date, .NET Framework 4, 4.5 and 4.5.1 will cease getting hotfixes and security updates.

This deadline, part of a new policy announced in August 2014, may be easier to meet since organizations can install .NET Framework 4.5.2 or newer versions and continue to stay supported. The .NET versions from 4.5.2 are described by Microsoft as "in-place" upgrades, which make the process a bit easier. An in-place upgrade doesn't require that the earlier .NET Framework version be uninstalled.

Microsoft carved out an exception for .NET Framework 3.5 Service Pack 1. Its lifecycle is still based on Microsoft's old policy. That is, the product lifecycle of .NET Framework 3.5 Service Pack 1 is still based the underlying Windows product lifecycle and will lose extended support at the same time that Windows does.

The end of extended support for SQL Server 2005 is scheduled for April 12, 2016. It takes several months to plan and execute a SQL Server migration, according to Microsoft.

Microsoft's technical upgrade guide (PDF) suggests that it's possible to perform an in-place upgrade from SQL Server 2005 to SQL Server 2014. The exception is a move from 32-bit SQL Server 2005 to 64-bit SQL Server 2014, where an in-place upgrade can't be performed.

(Editor's Note: A version of this news article includes news on Internet Explorer end of extended support on Redmondmag.com.)

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.