Re: Installing VS6 After VS.Net 2003
From: Gerald Hernandez (Cablewizard_at_spam_remove@Yahoo.com)
Date: 09/15/04
- Next message: Wart: "Re: MDI Child form in DLL"
- Previous message: Norm Cook: "Re: Windows default path"
- In reply to: Timothy Casey: "Re: Installing VS6 After VS.Net 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Sep 2004 09:29:31 -0600
This I have run into countless times in the past. I don't think it has
anything to do with VS7. The problem I usually have is due to the service
pack on client or build machine.
The setup package has different version of control(s) than the client
machine. When you run the package, it tries to upgrade the control on the
client machine. Client reboots, file protection kicks in and replaces the
changed file with the original file. Setup package notices it needs to
upgrade. Endless loop.
The way to fix is to manually edit the setup project and/or include specific
control versions.
When you go back and build on legacy machine, it uses the older version
controls, which don't need upgrading, so they are just ignored on install.
I have not made the jump to XP-SP2 yet. But am assuming this is the same
thing I have seen numerous times with Win2K. Exact same behaviour.
Gerald
"Timothy Casey" <ReplaceOhWithZeroNumbersOnly1195O@fieldcraft.biz> wrote in
message news:4147efc3$1_1@news.iprimus.com.au...
> 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 number@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@spam_remove@Yahoo.com> wrote in message
> news:eWduKVomEHA.2020@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
> >
> >
>
>
- Next message: Wart: "Re: MDI Child form in DLL"
- Previous message: Norm Cook: "Re: Windows default path"
- In reply to: Timothy Casey: "Re: Installing VS6 After VS.Net 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
