This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- How to block simultaneous installation
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 26, 2010
07:06 AM
How to block simultaneous installation
I am using InstallAnywhere 2010 to create the installer for my project. I am facing an issue with the muliple installations. The project executable can be invoked multiple times and there are multiple instances running at the same time. This creates problem during the installations. Is there any way to block simultaneous installations running? Or is there any way atleast to find the multiple instances running in the same system?
Thanks in advance.
Sathya
Thanks in advance.
Sathya
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 27, 2010
05:05 AM
Hello,
IA 2010 contains "Instance Management" feature (Project > Advanced). This will not prevent starting multiple installer, but this can prevent editing simultaneously the same installation path.
If this is not what you need, I guess you can prevent running a second installer by creating for example a lock file that contain pid of the installer process. Then when the installer is launched, check if lock file exists, and if exists, check the pid still exists .... if yes, exit the installer and if not, then you can proceed with the installation.
--Jerome
IA 2010 contains "Instance Management" feature (Project > Advanced). This will not prevent starting multiple installer, but this can prevent editing simultaneously the same installation path.
If this is not what you need, I guess you can prevent running a second installer by creating for example a lock file that contain pid of the installer process. Then when the installer is launched, check if lock file exists, and if exists, check the pid still exists .... if yes, exit the installer and if not, then you can proceed with the installation.
--Jerome
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)