Install Build singleInstanceCheck

Comments

5 comments

  • Avatar
    michiel

    Hi Lei,

    Currently <singleInstanceCheck> checks if any other InstallBuilder installers are running. Could you give more details about this requirement?

    Regards,

    Michiel

     

    0
    Comment actions Permalink
  • Avatar
    Lei Liu

    We use InstallBuilder to build an installer for a couple of our different component

    Say we have component A, B, C

    I understand if we run two installers of the same component, it will block it.

    For example, if we run two A.exe

    But in the case, I run A.exe first but then run B.exe is it supposed to be blocked?

     

    0
    Comment actions Permalink
  • Avatar
    michiel

    Hi Lei,

    > But in the case, I run A.exe first but then run B.exe is it supposed to be blocked?

    Right now, that is how singleInstanceCheck works. It checks for any running installers created with InstallBuilder. 

    You could workaround this by using <processTest> instead of <singleInstanceCheck> for example:

    <throwError text="Another instance of the installer is already running.">
        ...
      <ruleList>
       <processTest>
           <name>your-installer.run</name>
          <logic>is_running</logic>
        </processTest>
       </ruleList>
      ...
    </throwError>

    Would this work for you?

    Regards,

    Michiel

    0
    Comment actions Permalink
  • Avatar
    Lei Liu

    It can be hard in Mac OS as the MacOS process name shall be the one inside of the MacOS folder inside of the APP, and it could be the same for different Apps.

    For example, it can be MacOS for two apps, they will have same process name but in different APP folders.

    0
    Comment actions Permalink
  • Avatar
    michiel

    Hi Lei,

    Unfortunately there is currently no other workaround for performing a single instance check on OS X.

    Regards,

    Michiel

    0
    Comment actions Permalink

Please sign in to leave a comment.