4 ms·
OT, but on the .NET Framework versioning, the support lifecycle of 2.0/3.0/3.5 is a mess that needs to be cleaned up: http://support.microsoft.com/kb/2696944 h
by yuhong 13y ago
OT, but on the .NET Framework versioning, the support lifecycle of 2.0/3.0/3.5 is a mess that needs to be cleaned up:
http://support.microsoft.com/kb/2696944 http://support.microsoft.com/kb/2696944
The lifecycle policy of 3.5 SP1 should also be applied to 3.0 SP2 and 2.0 SP2, for example.
- shanselman 13y agoThanks, I've sent this note to the Lifecycle guy and I'll get you a response.
- jamshedd 13y agoThanks for the feedback Yuhong. As you correctly pointed out .NET 2.0 SP2 and .NET 3.0 SP2 are sub-components of .NET 3.5 SP1 so it makes sense to have these on the same lifecycle. The good news is that this is already the case, the Knowledge Base Article 2696944 clarifies that when .NET 3.5 SP1 is installed the same lifecycle will apply to .NET 2.0 SP2 and 3.0 SP2 too. This is the relevant snippet from that KB article - ...snip... However, Microsoft will provide support for the .NET Framework 2.0 and .NET Framework 3.0 components for customers who install the .NET Framework 3.5 for as long as the .NET Framework 3.5 remains in support. ...snip... Thanks, Jamshed Program Manager, .NET Framework Fundamentals team
- yuhong 13y agoBut why 2.0 SP2 and 3.0 SP2 has a different lifecycle if 3.5 SP1 is installed vs if it is not installed?