Re: Registering OCX programmatically

From: Thomas Scheiderich (tfs_at_deltanet.com)
Date: 06/02/04 

Date: Wed, 2 Jun 2004 12:47:25 -0700

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:OW0gb4MSEHA.3944@TK2MSFTNGP11.phx.gbl...
> Thomas Scheiderich wrote:
> > Not really a hang up.
> >
> > In my case, it is only going to work on one (maybe two) machines. It is
a
> > program they already have on their machines and we just move the project
> > folder over to replace the old folder.
> >
> > I agree with you on an initial install of a package. But what about my
> > changes that I am making in the last couple of days where I have moved
the
> > program over to the user about 10 times. Would I create a new package
for
> > each change I make? Seems a little much (maybe not).
>
> Not really. Especially if you're using a decent installer (like
> InstallShield). It's just a matter of firing up the installation builder
> and hitting the build button (no other changes required). The utility
> will pick up the changed files and add them to the package (replacing
> those that are already there).
>
> The PDW will probably even do this (if running in stand alone mode)....
> but the PDW is a last resort. There are several freeware alternatives to
> the PDW.
>
> Once the package is built, dump it on a server and notify the users to
> run it.
>
OK, I'll give it a spin.

Thanks,

Tom
> > Thanks,
> >
> > Tom.
>
> --
> Ken Halter - MS-MVP-VB - http://www.vbsight.com
> Please keep all discussions in the groups..