Install VC6 after VC7 ?

[David Wilkinson]

Does anybody know if there are any issues installing VC6 after VC7?

Right now I have VC5, VC7 and VC7.1 running on the machine, and they run
quite happily together. But they were installed in this order.

TIA,

David Wilkinson

 

[Jochen Kalmbach [MVP]]

Does anybody know if there are any issues installing VC6 after VC7?

Right now I have VC5, VC7 and VC7.1 running on the machine, and they run
quite happily together. But they were installed in this order.

Just to note: There is no offical support for VC5 and VC6 side-by-side
installation (of course support has already ended ;-) )

But see:
http://www.codeguru.com/Cpp/V-S/tips/article.php/c461/


--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

 

[David Wilkinson]

Just to note: There is no offical support for VC5 and VC6 side-by-side
installation (of course support has already ended ;-) )

But see:
http://www.codeguru.com/Cpp/V-S/tips/article.php/c461/

Jochen:

Yes, I know VC5 and VC6 will not work together because the debug DLL's
have the same name but the VC6 ones are not backward comaptible (was
that stupid, or what?). I will not use VC5 any more when (if!) I get VC6
working.

David Wilkinson

 

[jeanluc.nahon]

David,

I recently installed VC6 after VC7.1 and I did not run into any major
issues. Just be careful with your path, include and lib and you should
be fine.

- JL

 

[Nishant Sivakumar]

I have installed VC6 after VC7.1 without problems.
But my preferred order is VC6, VC7.1 and then VC2005.

 

[Doug Harrison [MVP]]

David,

I recently installed VC6 after VC7.1 and I did not run into any major
issues. Just be careful with your path, include and lib and you should
be fine.

I've given up installing system-wide environment variables. It just doesn't
work when multiple compilers are installed. They're not necessary for the
IDE, and for the command line, there are the vcvars32.bat files to set
things up.

Note that VC6 (or maybe it's just Visual Studio 6?) will install the
obsolete MS Java VM. To avoid this, create a zero-length file in %windir%
(e.g. C:\WINDOWS) named msjava.dll. Once installed, delete this file.

 

[Norman Diamond]

Does anybody know if there are any issues installing VC6 after VC7?

Do you want to change your JIT settings? Yes or no. By now I've forgotten
what I answered.

Can you guess what component is asking? You don't have to answer that
question though. Just wondering if you can guess. And can you guess if you
want the answer to be yes or no.

I don't remember any troubles though. Maybe I luckily guessed the right
answer.

 

[Jim]

Is VMWare or VirtualPC an option for you?

I use VMWare to isolate my programming environments and have been quite
pleased with the results.

 

[David Wilkinson]

Do you want to change your JIT settings? Yes or no. By now I've
forgotten what I answered.

Can you guess what component is asking? You don't have to answer that
question though. Just wondering if you can guess. And can you guess if
you want the answer to be yes or no.

I don't remember any troubles though. Maybe I luckily guessed the right
answer.

Norman:

I'm not quite sure what you are asking/saying here. Does it have
specifically to do with installing VC6 after VC7?

Speaking of JIT, that is one thing that does not work for me with VC5
and VC7 installed together (but in the "correct" order). When I am
running VC5, the JIT wants to open VC7 to do the debugging. I don't know
if that can be fixed, but I can live with it.

David Wilkinson

 

[David Wilkinson]

I've given up installing system-wide environment variables. It just doesn't
work when multiple compilers are installed. They're not necessary for the
IDE, and for the command line, there are the vcvars32.bat files to set
things up.

Note that VC6 (or maybe it's just Visual Studio 6?) will install the
obsolete MS Java VM. To avoid this, create a zero-length file in %windir%
(e.g. C:\WINDOWS) named msjava.dll. Once installed, delete this file.

Doug:

I don't think VC6 does anything with Java. It must just be Visual Studio.

David Wilkinson

 

[Doug Harrison [MVP]]

I don't think VC6 does anything with Java. It must just be Visual Studio.

Could be. I wouldn't chance it, though. I install only VC6 and VB6 when
installing Visual Studio 6, and my notes tell me to perform the msjava.dll
trick, even though I don't install InterDev or J++. I gotta follow my
notes.

 

[David Wilkinson]

Could be. I wouldn't chance it, though. I install only VC6 and VB6 when
installing Visual Studio 6, and my notes tell me to perform the msjava.dll
trick, even though I don't install InterDev or J++. I gotta follow my
notes.

Yesterday I installed VC6 on my laptop (which doesn't have VC7, so I
wasn't worried about it), and this did not happen. In fact this machine
has no copies of msjava.dll anywhere.

My desktop (the one that has VC5 and VC7 now) does have msjava.dll in
SYSTEM32. It is dated 2/28/2003, 926KB, version 5.0.3810.0. Is it not
supposed to be there?

David Wilkinson

 

[Doug Harrison [MVP]]

Yesterday I installed VC6 on my laptop (which doesn't have VC7, so I
wasn't worried about it), and this did not happen. In fact this machine
has no copies of msjava.dll anywhere.

My desktop (the one that has VC5 and VC7 now) does have msjava.dll in
SYSTEM32. It is dated 2/28/2003, 926KB, version 5.0.3810.0. Is it not
supposed to be there?

All I know is MS stopped supporting their Java VM, meaning no more security
updates or improvements, though the Apr-2004 settlement may have mitigated
that somewhat. They stopped including it in Windows as of WinXP SP1a. For
more, see:

http://www.microsoft.com/mscorp/java/faq.asp

My take is that if you already have msjava, it's probably OK, but if you
don't, and you don't need it, you should avoid installing it.

 

[David Wilkinson]

Does anybody know if there are any issues installing VC6 after VC7?

Right now I have VC5, VC7 and VC7.1 running on the machine, and they run
quite happily together. But they were installed in this order.

TIA,

David Wilkinson

Thanks, all, for the input.

Yes, as you all said, you can install VC6 after VC7. VC7 still works,
which is what I was worried about. I successfully transferred my app
from VC5 to VC6, so now I'm only 7 years behind, not 8. I may still move
it to VC8, but I just hate the .NET IDE for MFC work, though I have used
VC7.1 a lot for cross-platform non-GUI work.

Norman, now I understand what you were talking about. The installation
did ask if I wanted to change my JIT settings. I said no.

David Wilkinson

=====================

 

[Norman Diamond]

Does anybody know if there are any issues installing VC6 after VC7?

Do you want to change your JIT settings? Yes or no. By now I've
forgotten what I answered.
Can you guess what component is asking? [...]

I'm not quite sure what you are asking/saying here. Does it have
specifically to do with installing VC6 after VC7?

While installing Visual Studio 6 after Visual Studio 7.1, a popup asked if I
want to change my JIT settings. Allowable answers were yes or no. By now
I've forgotten what I answered. I don't know if the question came from
Visual Studio 6, or from some component of Visual Studio 7.1 detecting that
some change was being asked of it, or maybe from something else. Besides
not knowing which component wanted to impose the change, I don't know which
version's JIT settings were going to be affected by change. I don't know
what the old values of the settings were, nor what the proposed new values
were going to be. The popup allowed answers of Yes or No.

 

[Norman Diamond]

I successfully transferred my app from VC5 to VC6, so now I'm only 7 years
behind, not 8.

VC6 was still on sale in 2002, so you might think you're 3 years behind, but
you'd still be wrong. If you install VC6 SP6 then you can get bugs that
were released in 2005.

 

[Todd R. Jacobs]

FWIW
This registry key got modified when .NET was installed
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
Name = Debugger
changed to:
"C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" -p
%ld -e %ld

And a New Key was created called
PreVisualStudio7Debugger
with the value set to:
"C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\msdev.exe" -p
%ld -e %ld

Using this value reset the Debugger back to the old VS 6.0 debugger
You might want to saved the New .NET value in a different Key for future
reference

Todd

Does anybody know if there are any issues installing VC6 after VC7?

Do you want to change your JIT settings? Yes or no. By now I've
forgotten what I answered.
Can you guess what component is asking? [...]

I'm not quite sure what you are asking/saying here. Does it have
specifically to do with installing VC6 after VC7?

While installing Visual Studio 6 after Visual Studio 7.1, a popup asked if
I
want to change my JIT settings. Allowable answers were yes or no. By now
I've forgotten what I answered. I don't know if the question came from
Visual Studio 6, or from some component of Visual Studio 7.1 detecting
that
some change was being asked of it, or maybe from something else. Besides
not knowing which component wanted to impose the change, I don't know
which
version's JIT settings were going to be affected by change. I don't know
what the old values of the settings were, nor what the proposed new values
were going to be. The popup allowed answers of Yes or No.