.NET 3.0 installation

[code_wiz]

Hi, I am currently using VS 2005 (.NET 2.0) and want to install the .NET 3.0 framework and start working on it. I have installed the .NET 3.0 Now i am told that i will need to install the Windows SDK and .NET 3.0 components and then install the VS 2005 extensions for the .NET 3.0 When reading through the Windows SDK install link in MS site, it is suggesting to do several things, including un-installing the current Windows SDK and also says there are several known issues around this install. It is also asking to uninstall existing stuff like Document explorer etc. which i use with VS 2005 (for documentation). And the list of things to do looks pretty long :-( The current machine is my production machine where i develop 2.0 based apps / controls and i want to be careful when installing the 3.0, especially the Windows SDK. Can anybody share their experience on this bit - i.e. the Windows SDK instalaation bit. Oncei get over this step, i can happily install the 3rd bit - i.e. the VS extensions for .NET 3.0 :-) and have fun with .NET 3.0 fluff :-)

[Dave Kreskowiak]

If your just going to play with .NET 3.0 don't install it on your production machine. Install something like VirtualPC, install Windows on a new virtual machine, then Visual Studio .NET 2005 and all the .NET stuff. That way, you can play all you want safely without screwing up your production environment.

Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
     2006, 2007

[DotNetInterest]

"That way, you can play all you want safely without screwing up your production environment." Why??? Is .NET 3.0 not RTM'ed yet? It is RTM!!!!!! I would be worried only if it was a RCs or Betas, but with RTM release, MS should ensure that it does not screw up any production environment, especially the .NET 2.0 system. If they cannot assure that, they should not be releasing .NET 3.0 as RTM at all. They should keep it as Beta if the developer community will have to be cautious to use it in production machines running 2.0 framework (or use it via Vistual PC etc.).

[Pete OHanlon]

While .NET 3 is release, some of the Visual Studio extensions are CTP.

Deja View - the feeling that you've seen this post before.

[DotNetInterest]

Ahh! That explains the fear! Thanks. :-)

[Pete OHanlon]

Glad to help.

Deja View - the feeling that you've seen this post before.

[Dave Kreskowiak]

It's not so much fear. It's also the fact that you can easily screw up writing code that works fine under .NET 3.0, but will screw over his .NET 2.0 project if needs to make updates to it. If you still have to maintain that .NET 2.0 codebase you're better off dedicating one development environment to developing for .NET 2.0 and another for .NET 3.0.

Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
     2006, 2007