BT

Your opinion matters! Please fill in the InfoQ Survey!

Developers Petition Microsoft to Rename .NET Framework 3.0

| by Marcie Jones Follow 0 Followers on Aug 21, 2006. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

A group of developers are petitioning Microsoft to change the name of the announced ".NET Framework 3.0" back to "WinFX" or another less-confusing name.  The source of the confusion is that the .NET Framework 3.0 will still run on version 2.0 of the Common Language Runtime (CLR), which many consider to be "the .NET framework."  The first three CLR, .NET framework, and Visual Studio .NET releases have all gone in lockstep, making this proposed release the first break in their chain of dependence.  Mailing list members are already asking whether this new .NET Framework 3.0 release, expected late in 2006, will include new features promised for C# 3.0, such as LINQ, and what they will need to do to make their .NET 2.0 applications compliant with 3.0.  The petition, with 210 signatures at the time of this writing, notes that:

.NET has defined a very solid convention for version numbers: major.minor.build.revision. Major version increments indicate structural changes; minor version changes indicate breaking changes. .NET 3.0 is neither a major or minor version change – it’s not even the same product.

Jason Zander addresses some of these concerns from the Microsoft perspective in detail on his blog, noting that the team has always thought of WinFX as being the same thing as the .NET Framework.  Jason also elaborates in a Channel 9 video interview that the .NET Framework 3.0 will install both a 2.0 CLR and a 3.0 folder in the Microsoft .NET framework directory.  Also, LINQ will be incluced in approximately .NET Framework 3.5 (version number again subject to change), but it does not require changes to the CLR itself, which is why the LINQ CTP can run against the 2.0 version of the CLR.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT