Microsoft .NET framework 3.0

[wpshooter]

Are there any known reasons for NOT installing the Microsoft .NET framework version 3.0 ?

Thanks.

 

[Skitzer]

.NET Framework 3.0, formerly called WinFX, includes a new set of managed code APIs that are an integral part of Windows Vista and Windows Server "Longhorn" operating systems. It is also available for Windows XP SP2 and Windows Server 2003 as a download. There are no major architectural changes included with this release; .NET Framework 3.0 includes version 2.0 of the Common Language Runtime.

 

[Snapster]

Rather than quote directly from wiki like above, I'll say that there are not many good reasons why you shouldn't install it. If you have any of the framework's already the only thing you'll suffer is a little bit of disk space for the install.

 

[Bluestealth]

Originally posted by: Snapster
Rather than quote directly from wiki like above, I'll say that there are not many good reasons why you shouldn't install it. If you have any of the framework's already the only thing you'll suffer is a little bit of disk space for the install.

That and the ability to execute potentially exploitable code.... while a low risk, it still is one... which is why you should only install it if you need it....

 

[Nothinman]

Are there any known reasons for NOT installing the Microsoft .NET framework version 3.0 ?

Because you don't need to run any .Net apps that would require it?

 

[Schnieds]

Don't think of 3.0 as an upgrade to the existing framework, it isn't. The term "3.0" is just a bad decision by someone in MS product marketing. It is just an extra set of libraries that provide additional capabilities to the .NET Framework, but it does not change the existing .NET 2.0 Framework in any way. Just like Nothinman said, if you don't require any apps that utilize 3.0 libraries there is no reason to install it. although if you do it won't interfere with anything.

 

[Markbnj]

Originally posted by: Nothinman

Are there any known reasons for NOT installing the Microsoft .NET framework version 3.0 ?

Because you don't need to run any .Net apps that would require it?

Virtually all new Windows apps require 2.0 at this point. It will be some time before many (any) require 3.0, but eventually everyone who runs Windows (or a very large majority of that population) will have it installed.

 

[corkyg]

I got tired of being bugged for 2.x. I removed 1.0, 2.0, and installed 3.0. Everything works perfectly and no more "bugging" nags. 3.0 does the job perfectly.

 

[ObscureCaucasian]

Does 3.0 remove the need for 1.1? It took me forever to realize that even though I had 2.0 some apps needed 1.1 still.

 

[corkyg]

I removed both 1.1 and 2.0 - 3.0 handles it all. No complaints from anything anymore.

 

[Nothinman]

Virtually all new Windows apps require 2.0 at this point. It will be some time before many (any) require 3.0, but eventually everyone who runs Windows (or a very large majority of that population) will have it installed.

That seems a little optimistic, even Vista which was supposed to ship with tons of managed code doesn't have nearly as much as MS would have liked. But I have no doubts that most Windows users will have it installed in the near future but not because "all new Windows apps" will require it but because one or two key apps will.

 

[SoulAssassin]

Originally posted by: Nothinman

Are there any known reasons for NOT installing the Microsoft .NET framework version 3.0 ?

Because you don't need to run any .Net apps that would require it?

/thread