Page Comparison

All Windows systems block executable files that are currently in use, as device drivers, EXE, DLL and even JAR files. Normally, a running application is to be shut down before such files can be overwritten, for instance by an IzPack installer. This might fit most of the use cases IzPack is used with.

There can be situations where the application cannot be shut down at the installation time, but has to be updated anyway. This is where this new feature comes into the game.

...

Lets start with an example of install.xml:

<installation version="1.0">
 
  <info>
    ...
    <rebootaction>ask</rebootaction>
    ...
  </info>
 
  ...
 
  <native type="izpack" name="SetupAPI.dll">
    <os family="windows"/>
  </native>
 
  ...
 
  <packs>
    <pack name="Core files" required="yes">
      <description>The core files needed for this test</description>
      <singlefile
       src="plain/my_exefile_v1.exe"
       target="${INSTALL_PATH}/my_exefile.exe"
       override="true" blockable="auto"/>
    </pack>
  </packs>
 
</installation>

...

For a complete specification of the according elements and attributes see the documentation of <rebootaction> in the Header - <info> and the blockable attribute in one of the elements <file>, <fileset> or or <singlefile>.