The .NET Framework 3.0 adds new technologies to the .NET Framework 2.0, which makes the .NET Framework 3.0 a superset of the .NET Framework 2.0. You can think of .NET Framework 3.0 as an “additive” release to the .NET Framework 2.0, as contrasted with a generational release where software is revised across the board. (For example, the .NET Framework 2.0 was a generational release over the .NET Framework 1.0.)

The 3.0 Framework adds four new namespaces to the 2.0 Framework:

• Windows Communication Foundation (WCF)
• Windows Presentation Foundation (WPF)
• Windows Workflow Foundation (WF)
• Windows Cardspace

Reference: Deploying Microsoft .NET Framework Version 3.0

Overcoming Fear

So, supposedly the 3.0 Framework is completely “additive” and the existing 2.0 Framework remains untouched. Despite this reassurance, I still felt uncomfortable just installing things willy-nilly. I felt sure I would find some small print buried on MSDN warning us of some critical change to the .NET 2.0 Framework included in 3.0 that would cause all my existing applications to stop working. Feeling comforted when I couldn’t find any warnings and pressured by the need to prepare for the rapidly approaching Community Launch Event, I proceeded.

Proceeding

First, download the framework and run dotnetfx3setup.exe. This will download 30 MB and install the “additive(s)” for you.

You’re done! The .NET 3.0 Runtime Components are now installed!

My first action after installation was to open all my current projects and make sure they all still run. Sure enough, everything still works!

SQL Server Setup failed to obtain system account information for the ASPNET account. To proceed, reinstall the .NET Framework, and then run SQL Server Setup again.

This is caused when ASP.net is installed before enabling IIS. This is easily fixed using the following on the command line:

\WINDOWS\Microsoft.NET\Framework\<version>\aspnet_regiis.exe -i

References

• Avoiding Microsoft SQL Server 2005 deployment pitfalls
• ASP.NET IIS Registration Tool

Operating system not found

I rebooted again and everything was normal. Unfortunately, “Bessie” is so old that normal is very slow…especially when trying to run applications like Visual Studio. I haven’t been very concerned about updating because I mostly use my Apple iMac at home and I have a pretty cool PC at work. I’ve got my eye on one of the Intel Macs…must hold off as long as possible though.