 |
Back in September, I compared Microsoft’s Avalon (WPF) and Indigo (WCF) demo application Microsoft Max to one of those glitzy concept cars that automakers are always wheeling out, but which never appear in the product line. Apparently the comparison was more apt than I realized since Max has just wheeled off into the sunset. Dare Obasanjo points to a post at the Max team blog titled “Thank you: the Max project has concluded” which breaks the news:
Thanks to your participation, we were able to accomplish the goals of the Max project—to get customer feedback on new ways to approach software and services. If you’re interested in seeing where we go with these ideas, keep your eye on Windows Live.
Starting today, we will be disabling all downloads from our website. In the next week, we will be shutting down the Max services and our team forums. At that time, you will no longer be able to sign in to Max or share lists of photos with your friends. You will still be able to read news and browse the lists you’ve already shared and received.
I expect there will be some grumbling.
When Microsoft first announced Max a year ago, it was a photo cataloging and sharing application that really showed off the Avalon (now Windows Presentation Foundation) graphical interface technologies coming in Vista and being retrofitted to Windows XP. A lot of water has flowed under the bridge since then and now a new version of Max is available, but for some reason a limited RSS feed reader has been added. I’m not sure exactly what Max is supposed to be other than good looking, like one of those auto show concept cars. Download it here if you would like to take a test drive, but note carefully the system requirements (including .NET 3.0 RC1) and that it’s all beta code.
There are still developers protesting Microsoft’s renaming of WinFX as .NET 3.0, but it is proceeding in step with Windows Vista and Release Candidate 1 was released last week and can be downloaded here:
The Microsoft .NET Framework 3.0 (formerly known as WinFX), is the new managed code programming model for Windows. It combines the power of the .NET Framework 2.0 with new technologies for building applications that have visually compelling user experiences, seamless communication across technology boundaries, and the ability to support a wide range of business processes. These new technologies are Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation, and Windows CardSpace (formerly code named “Infocard”). Microsoft plans to ship .NET Framework 3.0 as part of the Windows Vista operating system. In addition, Microsoft is making these technologies available on Windows XP and Windows Server 2003. The following Community Technology Preview of .NET Framework 3.0 enables you to continue experimenting with early builds of these technologies, get acquainted with the development experience, and provide feedback to Microsoft.
…
Please note that the License Agreement in this pre-release version of the .NET Framework v3.0 does not allow usage in a live operating environment. Information about Go-Live possibilities can be found here.
…
This release supports Visual Studio 2005 RTM and is compatible with 2007 Microsoft Office system Beta 2 Technical Refresh.
I suppose I should update my categories – I’m still calling them Avalon, Indigo, and Infocard. Also to get up to speed, there’s David Chappell’s new MSDN paper, Introducing the .NET Framework 3.0.
Paul Krill at InfoWorld:
Microsoft has re-branded its WinFX technologies as .Net Framework 3.0 to clarify the naming convention for its developer framework, company representatives said on Friday..Net Framework 3.0 is planned for inclusion in Windows Vista, due out in early 2007. The framework features the Windows Communication Foundation Web services platform; the Windows Presentation Foundation presentation layer technology; Windows Workflow, for workflow; and the newly renamed Windows CardSpace, for identity management. CardSpace had been code-named InfoCard. Current .Net Framework 2.0 technologies, such as the CLR (Common Language Runtime), also are part of .Net Framework 3.0
“The .Net Framework has always been at the core of WinFX, but the WinFX brand didn’t convey this,” said S. “Soma” Somasegar, corporate vice president of Microsoft’s Developer Division, in his blog.
The Somasegar post is here and makes it clear that it is a name change only for all the .NET Framework 2.0 pieces. There are more details by following both the links, but there’s nothing that gets techies crankier than nomenclature so I expect there will be some complaints, particularly as this is a just a mash-up under a new name of technologies that previously had a separate life of their own. In any case, as expected (per Somasegar):
The .NET Framework 3.0 will still ship with Windows Vista, and will be available down-level for Windows XP and Windows Server 2003 as planned. This change doesn’t affect in any way the ship schedules of either Windows Vista or the .NET Framework 3.0 itself.
Update 6/21: Roy Osherove provides more information and a table that’s very helpful in puzzling out the .NET Framework versioning and future plans.
