I've got this to work following the approach described above.
Except for one thing.
I'v have a problem in the following scenario. Package A chains package B Package B runs a custom action to determine if package C should be chained In other words: A chains B, B may chain C
Is it possible to get directory from where the bootstrapper is launched?
"SourceDir" cannot be used because the msi packages are included within the bootstrapper (and thus SourceDir is not the location of the bootstrapper, but of the extracted msi files)
I have an installer with chained packages. One of the chained packages require java to be installed. This chained package is only installed if certain choices are made in the main package. Thus the complete installation will sometimes require java to be installed (depending on the choices ...
The file is created through a custom action under InstallInitialize. So it is not available under "File and folders"
During install we have a custom action checking if the file exists already. If the file already exists we skip a couple of dialogs and the file is not recreated (saves the user some ...
During install we me ask the user where our program can save certain files.
If the user chooses a network path (e.g. \\server\share\path) the server may require a password and login to that path. The user enters these details during browsing to that path.
FOLLOW US