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

Oh Data! Microsoft Ships First Major OData Update in Nearly 8 Years

Microsoft today shipped a preview of OData .NET 8. OData v7.0 was released in August of 2016.
Full Stack Hands-On Development with .NET

In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.
.NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

"We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."
Creating Reactive Applications in .NET

In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.
AI for GitHub Collaboration? Maybe Not So Much

No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.