InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Developers Petition Microsoft to Rename .NET Framework 3.0

Posted by Marcie Jones on Aug 21, 2006

Sections
Development
Topics
Artifacts & Tools ,
.NET ,
.NET Framework
Tags
WPF ,
WinFX ,
Windows Workflow Foundation
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.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.