Installing VS on two operating systems?

  • Thread starter Thread starter lallous
  • Start date Start date
L

lallous

Hello

If one has two operating systems on two different partitions, say
Vista and XP.

Is there is a way to install VS2005 on one partition and make it work
on both operating systems, without needing to install VS2005 on both
OSes (so that the registry is patched correctly) ?

Regards,
Elias
 
What are you trying to do ????
have you ever try to drive a second car by beeing on a first one ?
 
lallous said:
Hello

If one has two operating systems on two different partitions, say
Vista and XP.
Click to expand...

You know, you can do this with Vista.

http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx
Is there is a way to install VS2005 on one partition and make it work
on both operating systems, without needing to install VS2005 on both
OSes (so that the registry is patched correctly) ?
Click to expand...

That answer should be no, and you shouldn't even try such a thing. It's too
ridiculous.
Two different registries would be in play I would suspect, along with
different versions of common Dll(s) working between the two O/S(s), etc,
etc.
 
Hello

Yes indeed, there would be two different registries, but most of the
files are quite the same: MSDN files, .lib and header files, etc...
So why consume the disk space twice?
 
lallous said:
Hello

Yes indeed, there would be two different registries, but most of the
files are quite the same: MSDN files, .lib and header files, etc...
So why consume the disk space twice?
Click to expand...

Well, you should let this sink in.

One doesn't develop solutions like this. You're asking for trouble on the
intended platform when said application is deployed. Just because both
O/S(s) have similar files Dll(s), libs, etc etc doesn't mean that a solution
is going to run on a given platform.

You cannot expect that a solution that was built on the Win 2K platform is
going to run on Win XP. You cannot expect that a solution built on Win XP is
going to run on Win Vista.

Although Dll(s), Lib(s) etc etc. will have the same filename, they are
different versions of them, common ones or not, that can be specific to a
given platform.

The rule of thumb should be you develop a solution to be deployed and ran on
its intended platform. Solution development on Win 2K to be deployed and ran
on the Win 2K platform, XP for XP, and Vista for Vista etc, etc.

If you want to know what Dll Hell is about, then you deploy Dll(s) into the
System32 directory that are intended to run on a specific platform replacing
like Dll(s) on that platform and watch applications brake that are dependent
upon a particular version.
 
Back
Top