I have a Windows Server 2003 development server that we use to hose a
bunch of internal web servers. The box is about 4 years old but does
the trick.

A developer on my team wants to install .Net frameworks 3.0 and 3.5.
All web services are using only 2.0 and I see no point in installing
framework that we may need someday. It's true that we will eventually
use more WCF and need it then, but not yet.

When I shared my thoughts, I was asked "what's the harm?". To do this
I didn't have a good answer. I'm a developer as well and by no means
a system admin.

Does anyone out there know of any negative impacts on performance or
anything else when having .Net frameworks installed? If you have any
links to documentation, that would be great to. I've searched but
came up with nothing.

Thanks!

>I have a Windows Server 2003 development server that we use to hose a
>bunch of internal web servers. The box is about 4 years old but does
>the trick.
>
>A developer on my team wants to install .Net frameworks 3.0 and 3.5.
>All web services are using only 2.0 and I see no point in installing
>framework that we may need someday. It's true that we will eventually
>use more WCF and need it then, but not yet.
>
>When I shared my thoughts, I was asked "what's the harm?". To do this
>I didn't have a good answer. I'm a developer as well and by no means
>a system admin.
>
>Does anyone out there know of any negative impacts on performance or
>anything else when having .Net frameworks installed? If you have any
>links to documentation, that would be great to. I've searched but
>came up with nothing.
>
>Thanks!

The only thing you should know is that .NET 3.0 hoses unidrv.dll. It
causes PCL XL errors and you'll have to get a recently released KB fix
for it.

- Thee Chicago Wolf