Visual Basic - VS SP6 question

Author

VS SP6 question

Vlad

2004-03-31, 2:30 pm

I installed my VB6 app on user's machines awhile ago. Since that I did not
add or change any references in my project. When I make any changes I just
compile and replace an old executable of the program on user's machines with
a new one. So far no problem.
If I'll install VS Service Pack 6 on my development machine, then compile my
project and replace executables on user's machines with a new one, may I
expect any problem?
In other words, do I have to prepare a new setup program for my project and
run it on every user's machine?
Thank you
Vlad

Ken Halter

2004-03-31, 2:30 pm

It would be best to create a new package. There are several things that can
go wrong if you're trying to run the app on a PC that has older components
than the dev PC has. That's one reason that you should distribute the oldest
version of a component that your app will work with... and why the
components in the following folder (below) seem so old. They're basically a
"minimum requirement" that won't be over-written on most systems because
newer versions are almost always already there.

C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
"Vlad" <vovan.c@verizon.net> wrote in message
news:eWldq10FEHA.2600@TK2MSFTNGP12.phx.gbl...
> I installed my VB6 app on user's machines awhile ago. Since that I did not
> add or change any references in my project. When I make any changes I just
> compile and replace an old executable of the program on user's machines
with
> a new one. So far no problem.
> If I'll install VS Service Pack 6 on my development machine, then compile
my
> project and replace executables on user's machines with a new one, may I
> expect any problem?
> In other words, do I have to prepare a new setup program for my project
and
> run it on every user's machine?
> Thank you
> Vlad
>
>

MikeD

2004-03-31, 4:30 pm

"Vlad" <vovan.c@verizon.net> wrote in message
news:eWldq10FEHA.2600@TK2MSFTNGP12.phx.gbl...
> I installed my VB6 app on user's machines awhile ago. Since that I did not
> add or change any references in my project. When I make any changes I just
> compile and replace an old executable of the program on user's machines
with
> a new one. So far no problem.
> If I'll install VS Service Pack 6 on my development machine, then compile
my
> project and replace executables on user's machines with a new one, may I
> expect any problem?
> In other words, do I have to prepare a new setup program for my project
and
> run it on every user's machine?
> Thank you

Theoretically, it *should* still run, but I wouldn't want to test that
theory with a production app in a production environment.

But what would the point of recompiling and giving the users a new EXE if
you're not going to install the SP6 versions of components (the SP6 runtime,
SP6 versions of controls, etc.)? Until you're ready to create a new setup
package and install it on users' machines, you probably shouldn't apply SP6
to your dev or packaging (if they're different) box.

Mike

Vlad

2004-03-31, 5:31 pm

Ken and Mike,
Thank you very much.
Vlad

"Vlad" <vovan.c@verizon.net> wrote in message
news:eWldq10FEHA.2600@TK2MSFTNGP12.phx.gbl...
> I installed my VB6 app on user's machines awhile ago. Since that I did not
> add or change any references in my project. When I make any changes I just
> compile and replace an old executable of the program on user's machines
with
> a new one. So far no problem.
> If I'll install VS Service Pack 6 on my development machine, then compile
my
> project and replace executables on user's machines with a new one, may I
> expect any problem?
> In other words, do I have to prepare a new setup program for my project
and
> run it on every user's machine?
> Thank you
> Vlad
>
>

Sponsored Links