A while back, I wrote about migrating from .NET 1.1 to .NET 2.0. I wrote that post almost a year ago, but it is still one of my highest traffic posts to this date. Well, it’s been a good 6 months now since .NET 3.0 has been on the scene, yet I haven’t written anything about migrating to it from the earlier versions.
Here’s the rub… there’s not much to write! You see, .NET 3.0 is really .NET 2.0 with a bunch of extra libraries (DLLs) added to it. There are no changes to the underlying runtime and base class libraries from the .NET 2.0 Framework!
In a nutshell:
- Installing the .NET 3.0 Framework on a machine that already has the .NET 2.0 Framework should not cause any impact to applications on that machine. (See Thomas’s post.)
- Installing the .NET 3.0 Framework on a machine that has only .NET 1.0/1.1 will have the same impacts as installing the .NET 2.0 Framework on that machine. (See my old post again.)