Microsoft’s .NET Framework is now fully released. There is a handy page of links to the various downloads you might want. Of all Microsoft’s releases in this busy November, this is the most significant.
Why? Here’s what is in .NET Framework 3.0. There are four major pieces. Windows Presentation Foundation (WPF) is an alternative GUI API for Windows, based on a new XML language (XAML) and incorporating the code-behind concept first seen in ASP.NET. Although it is primarily for Windows, Microsoft is promising a cross-platform XAML runtime called Windows Presentation Foundation/Everywhere. On Windows, WPF apps are rendered using DirectX, giving it impressive multimedia capabilities. Summary: biggest change to the Windows API since its first release.
Windows Communication Foundation is a communication framework based on XML web services. If you are familiar with Windows development, the easiest way to define WCF is by what it replaces: ASP.NET web services, MSMQ (Microsoft Message Queue), COM+ (also known as Transaction Server) and Distributed COM, .NET Remoting.
I won’t say that WCF replaces all of COM, though perhaps it might do eventually. COM has many faces.
Windows Workflow Foundation is less important than WPF or WCF, but still interesting as a framework for workflow applications. It fits well with Sharepoint and Office 2007 as a way to program enterprise portals.
Windows CardSpace is an abstraction layer for identity management and authentication. Unlike Microsoft Passport, CardSpace is not itself an identity provider, but a rather a system that works with multiple identity providers. If widely adopted, it will help the Internet move on from the nightmare of usernames and passwords. IE7 is a CardSpace client.
When Microsoft first announted the above pieces, they were meant to be exclusive to “Longhorn”, now called Windows Vista. The company realised that this would stall adoption, possibly fatally, so it was decided to make it a free download for Windows XP as well as part of Vista. That makes .NET Framework 3.0 a viable development platform now, rather than in five year’s time (or never).
Like any new technology, this one could fall flat on its face. Time will tell whether it is really significant, or turns out to be a backwater in the latter days of Windows. Unlike Vista and Office, it is not an immediate profit centre for Microsoft, but in the longer term it is critically important to the company as an update to the Windows platform.
In addition to the marketing and identity problem, .NET 3.0 has a documentation problem.
I have successfully installed the 3.0 Framework without issue, but I see little evidence of it on my system. Shouldn’t there be something in my Programs menu? Control Panel? Administrative Tools? Not even a post-install readme that says what I actually installed? I want to know what I can do with what I installed.
I don’t see any new references in VS.NET. I do see C:WINDOWSMicrosoft.NETFrameworkv3.0 with some MSI files in it. Do I need to run each one? There is a WPF.msi. Do I have to run it to create WPF apps? Am I ready to run WPF apps?
Someone at MSDN has dropped the ball. Big time.
Sounds like you’ve installed the runtime, which is pretty much invisible. The idea is that developers install the latest Windows SDK, currently here:
Windows SDK
though it changes quite frequently.
The docs are in there.
Tim
Hi, Tim. Thanks for replying so promptly.
I didn’t try the SDK because the page says it is the SDK for Vista all over it. Everywhere, that is, except for the list of supported operating systems. I have downloaded the SDK and enqueued it for installation on XP Pro SP2.
Thanks again.