PDA

View Full Version : Self Registering Executable



NewsArchive
09-08-1997, 12:00 AM
I have an EXE that causes ISE2 to generate a message "Unable to
register the following files : myapp.exe". Once you click ok the
application is installed and runs fine. Is there a way to turn off the
"OLESelfRegister" variable for the installion of this EXE.

NewsArchive
09-13-1997, 12:00 AM
Sean,

If your executable has dependencies, the dependencies should be installed
and registered. If you bypass self-registration your executable may not
work if a certain operating system does not have all the files, your executable
depends on, already installed.

To bypass self-registration you will need to keep the file uncompressed on your
distribution media or inside of SUPPORTDIR. Then you will need to write an
express extension(.dll or .exe) which will copy this file from source to the
destination directory.

You can find additional information, about using express extensions from the
Express help as well as www.installshield.com

Dan

Sean Jones <sean30@ix.netcom.com> wrote in article <3414087d.0@news.installshield.com>...
> I have an EXE that causes ISE2 to generate a message "Unable to
> register the following files : myapp.exe". Once you click ok the
> application is installed and runs fine. Is there a way to turn off the
> "OLESelfRegister" variable for the installion of this EXE.
>
>
>
>

NewsArchive
11-26-1997, 01:00 AM
Hi,

I ran into the same problem, and manually registering the exe with
LaunchAppAndWait works fine.

However, I haven't tried this out (yet), but, how is the situation handled
where the exe is locked during installation time. Which exe is then
registered, the existing one, or the one that is copied over ?

e.g. Let's say your updating myserv.exe in the directory c:\MyApplication.

During the file transfer, myserv.exe is locked, so the copied over version
is moved to a tempory location somewhere.
After the file transfer you call LaunchAppAndWait to execute the command
c:\MyApplication\myserv.exe /REGSERVER. This will simply re-register the
current exe and not the new one !

This can't hurt offcourse as long no new information is required in the
classes, but what if ...

Any comments on this or has any one experience with this.

Regards,
Denis Doornaert.

NewsArchive
11-28-1997, 01:00 AM
Denis Doornaert <sky58710@skynet.be> wrote in article
<347c7155.0@news.installshield.com>...
>
> During the file transfer, myserv.exe is locked, so the copied over
version
> is moved to a tempory location somewhere.
> After the file transfer you call LaunchAppAndWait to execute the command
> c:\MyApplication\myserv.exe /REGSERVER. This will simply re-register the
> current exe and not the new one !

What about checking the version of the exe in c:\MyApp with the
VerGetFileVersion function? If it's the wrong (older) version just place a
little .BAT file in the startup folder which does the job and removes
itself afterwards ....

Just an idea. I've not tested it ...

Regards,
--
Stephan Hagedorn
Software Development
dSPACE GmbH, Gemany
SHagedorn@dspace.de
http://www.dspace.de

NewsArchive
11-28-1997, 01:00 AM
Hi,

Thanks for the reply.

Your proposed solution propably works (not tried yet), but, it's simply to
much work.

These things should be build in in the functionality of IS5. It should be
all taken care off for you.

This is what IS should do : installing applications under all circumstances.
The only input required from the developer should be to indicate which
applications to install.

Regards,
Denis.

NewsArchive
12-03-1997, 01:00 AM
No offense meant for you personally, but this is a brain dead approach to
registering exe's. I was using the non-batch method until my superiors
started complaining about the length of time it took to install our product
(30MB or so). I thought no big deal, I'll switch to batch. Well, imagine
my surprise when all of the exe's failed to register. This is not an
acceptable lack of functionality for IS5. Nowhere in the help file does it
state you will not be able to register exe's using the batch method. This
ability needs to be a top item for the next maintenance release. If I have
to continue to write DLLs to extend the functionality of InstallShield 5 Pro
(I'm at 3 already), I might as well ditch your product altogether.

Jeremy Smith
ObjectAutomation

InstallShield Corporation wrote in message
<01bcf9c4$1e4b7860$95c7c5d0@annavuong.installshield.com>...
>You will need to use the non batch method.
>Move the Self registering EXEs out of the Self
>Registering file group and add lines to your script to call
>LaunchAppAndWait
>with the "/Regserver" param on each of your EXEs.
>You will need to write a DLL to handle uninstall of these EXEs.
>--
>Anna
>
>Gary West <westg@flyt.com> wrote in article
><3479f99d.0@news.installshield.com>...
>> Does InstallShiled handle self registering executables? I have several
>DLLs
>> and EXEs in a file group marked shared and self-registering.
>InstallShield
>> handles the DLLs. It fails to register the EXEs.
>>
>> I am using the batch registration. Enable(SELFREGISTERBATCH)
>> After calling Do(SELFREGISTRATIONPROCESS), ERRORFILENAME lists all of the
>> EXEs I was trying to register.
>>
>> Calling LaunchAppAndWait on the EXE with the argument /regserver
>registers
>> the EXE.
>>
>> When I uninstall the app, I am ask if I want to unregister the EXE.
>>
>> Gary West
>> westg@flyt.com
>>
>>
>>
>>
>