Re: Register OCX
- From: Jan Hyde <StellaDrinker@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 01 Nov 2006 17:07:37 +0000
"Esha" <aaa@xxxxxxxxxxxxx>'s wild thoughts were released on
Wed, 1 Nov 2006 11:47:00 -0500 bearing the following fruit:
My application uses many third party OCXs and DLLs. It was installed on many
user workstations via setup. The time taken by setup is pretty big.
If I make changes in my application and those changes do not involve
additional OCXs or DLLs, then replacement of the exe of my application is
enough to upgrade to the newer version and it's done automatically without
user interaction.
Now I need to add a new OCX to my project. Automatic upgrade won't work,
because I need to register that OCX on every user machine. To run setup is
not an option because it's going to take a lot of time. Another option is to
create a simple project using that OCX, create setup for it and run on every
workstation. This approach is not good too, because the average user might
not have enough knowledge to run setup. If I will do it myself, I need to
interrupt the user and I wouldn't want to do that.
Third option is to create some package - user double clicks on the file and
without any dialogs, questions etc, a new OCX is registered.
But how to create that package, I have no idea. What it should be, some kind
of exe, batch file or what?
Any suggestions please
What are you using to create your setup program now?
Jan Hyde (VB MVP)
--
How many Flies does it take to screw in a light bulb?
Two - the trick is getting them in there!
.
- Follow-Ups:
- Re: Register OCX
- From: Esha
- Re: Register OCX
- From: Esha
- Re: Register OCX
- References:
- Register OCX
- From: Esha
- Register OCX
- Prev by Date: Re: Database transactions and data-state flags
- Next by Date: Re: LZW .Z Decompression?
- Previous by thread: Register OCX
- Next by thread: Re: Register OCX
- Index(es):
Relevant Pages
|
