Hi, Sorry but I have no answer to your question 😞 I just have same kind of issue and I had to remove all indirection . Is that issue have been fixed in IS 2011 (Flexera actually communicates on this standalone build topic, so may be some improvement or bug fixing ....) ? Bernard. ... View more

We got same kind of issue (lock folders after uninstalling only on Windows 7) it was related here some time ago http://community.flexerasoftware.com/showthread.php?t=190916 After some investigation we discovered it was because COM extract at build option was not working fine with a mixed (dual) COM/.NET dll. We removed COM extract at build option and set registrey keys "manually" for COM and issue was fixed . Bernard. ... View more

Hi, May be you could try to manage 2 prerequisite installers based on your two msi files (the one 32 bits OS and the one for 64 bits OS). In the installation condition of each prerequisite you could check for appropriate conditions. In our case we have one different installer for each type of OS (32 bits or 64 bits), user has to choose the right one ; therefore unfortunately we did not test above solution. Regards, Bern ... View more

You should set your "Display .NET Option Dialog" to "No" (instead of "Yes"). You will not get FW .NET 2.0 in the prerequisite setup list but information will be displayed when fw installation will proceed (at the of button of installation window). Bernard. ... View more

Hi, You will may be find something about that here : http://support.microsoft.com/kb/905238/en-us Regards, Bernard. ... View more

Hello, I found this : http://community.acresso.com/showthread.php?t=155107 It is a little bit old but may be this could help. Bernard. ... View more

Hello, We did copy all our merge module stuff (ours and those provided by IS installer and patches) under the same folder (C:\Program Files\Macrovision\IS 12 StandaloneBuild\Modules\i386 because at this time we were on IS12). Bernard ... View more

Hi, May be you should try with a full path for your merge module folder (we were able to build our install like this) Bernard. ... View more

Hi everyone, I assume your installation is an Installscript project ? I know its not easy (and usually impossible) to migrate your installer to MSI project , but in this case for COM components, there is a "COM extract at Build" (and no more when launching your installation set up). This means, at installation runtime,it not a requirement to have all dependencies available for registration (dependencies are required only when building your installation setup) . Bernard. ... View more

Hi, Is the set up you are trying to launch through custom action, also a .msi ? If yes, you could get error message from WI because launching more than one .msi installers in the same time is bad :-). In this cas you could deal with this, launching your embedded set up as a prerequisite . Bernard. ... View more

If your new installer perform a major upgrade it should first unsinstall previous version of your application (cf my previous answer). Bit if it does not (minor upgrade, this means you did not change Product Code) , if files are not updated, this could mean that your file versions are not managed correctly (increasing file version is a requirement, Windows Installer does not deal with dates like it is with Installscript projects) . If some of your files cannot be versioned, you need to associate versioned "Companions files" for those files (typically .txt or any other kind of file with no version). Bernard. ... View more

Hi, For point 1) , your application 1 is not uninstalled because your new installation (application 2) is not a major upgrade . Just modify your application Product Code with new guid to make your new installer a major upgrade. Bernard. ... View more

Hi, Did you perform a major upgrade of your installation ? if yes, it should work. if no, according documentation, you should check the following : -if your new compopent was added to an existing feature, check Windows installer is 2.0 or later because Windows Installer 1.x requires new components in an upgrade package, to be placed in new features for minor upgrades. I hope this help, Bernard. ... View more

Hi, Did you already install this hotfix ? http://support.installshield.com/kb/view.asp?articleid=Q113498 Regards, Bernard. ... View more

Hi, For .NET fw installation you should use a Prerequisite (instead of a custom action). Anyway ,I think you should get issue running runtime fw .NET 3.0 installer (msi) in the same time your (msi) installer is running. Microsoft .NET Framework 3.0 is available if you download and install following installShield update : InstallShield 2008 MSI .NET Setup Prerequisites. Afterwards you can go in ApplicationData->Redistributables and select appropriate SetUp Prerequisite. Regards, Bernard ... View more