Hi, Cosmin,
cosmin wrote:Note that what you need is not supported by Windows Installer and Microsoft recommends to register the package with Windows Installer.
My installation consists of two features. User is allowed to select only one of them. First feature installs product onto PC, second one installs in onto separate hardware device, connected to PC as a removable drive. So, there is no any logic to leave any trails in registry, if user chooses second option.
cosmin wrote:Also, you could try to manually condition the standard actions (through Orca), but I'm not sure if it will work and most likely the package will have validation errors.
I did not found any information on Microsoft about whether it is allowed to set conditions for RegisterProduct, RegisterUser, PublishProduct, and PublishFeatures Actions in InstallExecuteSequence and AdvtExecuteSequence tables. But I have found that some people recommend that:
http://www.prairienet.org/~pops/msi_tips.html
http://www.installsite.org/pages/en/msi/isd.htm
I set condition for these actions to "&FirstFeature = 3" with Orca, and it works just fine. So I'm going to try this way.
But I need to make single-file EXE installation with LZMA compression. So, the next question is:
Is it possible in Advanced Installer to modify generated MSI with Orca, and then build final single-file EXE installation manually (probably, using 7-zip, AI\stubs\setup.exe, notepad for editing ini file, copy /b, binary editors, whatever)?
Thank you,
Olexa
FOLLOW US
Get the latest news in Application Packaging