Multiple .Net framework version

[Fred]

Is there any disadvantages to having more than one versions of the .net
framework installed on the same computer?
would that reduce the performance of the computer? or are they just a bunch
of dlls sitting on the hard drive

could someone clarify this?

thanks,
Fred

 

[Jesse Houwing]

Hello Fred,

Is there any disadvantages to having more than one versions of the
.net
framework installed on the same computer?
would that reduce the performance of the computer? or are they just a
bunch
of dlls sitting on the hard drive
could someone clarify this?

Just a bunch of dll's. Don't worry

Jess

 

[Matt F]

I got pointed to this link when I asked the same question recently. Haven't
actually implemented it yet, so I'd be curious to see how it goes.

All indications are that it should work just fine, but converting an
existing app targeting 1.1 framework to a VS2005 solution is a one way
street - so I'm being extra cautious with this one.

http://blogs.msdn.com/yaleeyangmsbl...g-visual-studio-2005-that-target-net-1-1.aspx

You go first and let me know how it goes.

 

[Matt F]

Please pardon me --- I posted this response to the wrong thread --- sorry
about that.

 

[Mr. Arnold]

Is there any disadvantages to having more than one versions of the .net
framework installed on the same computer?
would that reduce the performance of the computer? or are they just a
bunch of dlls sitting on the hard drive

could someone clarify this?

You can have multiple .Net Frameworks on the machine with each residing in
its own space.

This can be done, because a .Net solution can be deployed to the machine
that is dependent upon the 1.1 Framework.

While on the other hand, a .Net solution can be deployed to the machine that
is dependent upon the 2.0 Framework.

A .Net Framework does not execute. It's just a library that has predefined
solutions that an application written in a specific .Net language can call
upon the solutions in the .Net Framework to provide a solution.