Lifecycle Policy FAQ—Microsoft .NET Framework

Back to Microsoft Lifecycle home page
 

NOTE: This FAQ was updated on February 16, 2017. 
 

What is the Microsoft Lifecycle Policy for the .NET Framework?
What is a component?
When does .NET Framework 4.5.2 reach end of support?
Why did the support for .NET Framework 4, 4.5 and 4.5.1 end on January 12, 2016?
Does this support change affect any previous versions of .NET Framework such as .NET Framework 3.5 SP1?
Will I need to recompile/rebuild my applications to use .NET Framework 4.5.2?
Are there any breaking changes in .NET Framework 4.5.2? Why do you include these changes?
The .NET Framework is also middleware in other Microsoft products such as Exchange Server, SQL Server, Dynamics CRM, SharePoint, and Lync. Do I need to make any updates to these products if they are using .NET 4, 4.5, or 4.5.1?
When I installed Visual Studio, it installed a version of the .NET Framework. Does this mean the version of the .NET Framework that was included with Visual Studio takes the Lifecycle Policy of Visual Studio?
What is the Lifecycle Policy for the different versions of the .NET Framework?

The information on this page is subject to the Microsoft Policy Disclaimer and Change Notice. Return to this site periodically to review any such changes.
 

Properties

Article ID: 17455 - Last Review: 15/02/2017 - Revision: 29

Microsoft .NET Framework

Feedback