YES there IS a problem, although it is possible that your customers will see
it first...
I have VB6 and VB7 running on the same machine, and products compiled and
packaged by VB6 on that machine would require the customer to reboot their
machine during the installation process for a particular un-specified series
of component upgrades. The upgrade failed quietly, and on reboot and rerun
of setup, the same request was made to reboot and rerun setup. This problem
only became apparent after the release of WinXP-SP2 on a package that had
been installing perfectly to older instances of WinXP.
The experience was very embarrassing, and I have since returned to a legacy
system (an old Win98SE box) with no VB7 for compilation and packaging. The
problem could be Win XP's SP2, it could be VB7, or it could be both. I have
not had any constructive feedback yet on whether VB7 users have experienced
the same problem since the release of WinXp-SP2 - So I'll be sitting on my
VB7 license for at least another ninety days before beginning to incorporate
VB7 into my development schedule...
--
Timothy Casey GPEMC! >> 11950 is the
nu****@fieldcraft.biz 2email
Terms & conditions apply. See
www.fieldcraft.biz/GPEMC
Discover the most advanced speed comprehension application at:
www.fieldcraft.biz/shop <BRef
http://www.fieldcraft.biz/ki.htm >
"Gerald Hernandez" <Cablewizard@sp*********@Yahoo.com> wrote in message
news:eW**************@TK2MSFTNGP09.phx.gbl...
One of my development PC's died, and I need to have legacy VS and VS.Net
installed at the same time. On the now dead PC, I had VS6 installed prior
to installing VS.Net. This worked just fine.
On my working PC, I already have VS.Net installed, but not VS6.
My question, will installing the older VS6 with VS.Net already installed
give me problems with VS.Net. Or should I first remove the VS.Net, install
VS6, then re-install VS.Net?
Gerald