A rich new JavaScript code editor spreading to several Microsoft web sites

Re:A rich new JavaScript code editor spreading to several Mi... by yuhong on Friday August 02, 2013 @03:33AM (#6145777)

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

The lifecycle policy of 3.5 SP1 should also be applied to 3.0 SP2 and 2.0 SP2, for example.

[ Parent | on HN ]

Re:A rich new JavaScript code editor spreading to several Mi... by jamshedd on Monday August 05, 2013 @09:32PM (#6164342)

Thanks 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

[ Parent | on HN ]

Re:A rich new JavaScript code editor spreading to several Mi... by yuhong on Monday August 05, 2013 @10:01PM (#6164434)

But why 2.0 SP2 and 3.0 SP2 has a different lifecycle if 3.5 SP1 is installed vs if it is not installed?

[ Parent | on HN ]

Re:A rich new JavaScript code editor spreading to several Mi... by shanselman on Friday August 02, 2013 @07:13PM (#6150249)

Thanks, I've sent this note to the Lifecycle guy and I'll get you a response.

[ Parent | on HN ]