Hey Fredrik, did you ever find out why your unmanaged dll did not work anymore? I've got the exact same problem when I upgraded to IS2014 (from 2012Spring). The dll I use is an unmanaged wrapper for a manged code. However, the stuff is quite old and refactoring the code is a big effort... Best Regards, Frank ... View more

Hi, I had the same issue some time ago.... My solution: You must evaluate the "IS_MAJOR_UPGRADE" or "UPGRADINGPRODUCTCODE" property to control the UI sequence and the texts being displayed in the dialogs. Otherwise the UI sequence runs completely as if it was a new installation. Then you can define a button "Just Upgrade" on the InstallWelcome dialog, that is only displayed depending on the property "IS_MAJOR_UPGRADE", and which allows to skip all dialogs and jumps right to the "ReadyToInstall" dialog. Take care that you migrate the feature states and that custom properties that are set correctly! ... View more

Maybe you have a look at "Multi-Instance Installations" under Media > Releases > Product Configuration. Of course you have to follow some rules e.g. directories, COM registrations, registry.... ... View more

The standard feature selection dialog does not refresh itself. Instead you could "clone" and recall the dialog as described here: http://setupprogram.blogspot.de/2012/09/condition-based-dynamic-feature.html. Or you build up your own dialog...maybe try InstallScript? ... View more

Also feature prerequites should have a condition that evaluates to "true" when the prerequisite is installed successfully. Using a registry key might be the easiest way. The driver package surely writes a version string into the registry, that you can use as installation condition. So when you update the feature you might update the driver at the same time when the version is increased. Alternatively you can just skip the conditions. Then the feature prerequisite is installed every time you run the setup or perform an update. In this case the driver package will update or reinstall itself. Does this make sense to you? ... View more

Hi, I am experiencing a similar problem and have not found a solution yet. In my BasicMSI project I have a feature prerequisite that forces a reboot. The reboot occurs when the feature selection has already been made at the end of the UI sequence. When the system restarts the setup resumes as expected - so far so good. However, it will start from the very beginning without evaluation any properties and re-runs the feature selection. I would expect that the setup resumes with remembering the previous feature selection and with a different dialog sequence by evaluating the RESUME property. Before the reboot I can see that IS CA "ISInstallPrerequisites" writes a registry key in HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce. String is "ISSetupPrerequisites" and the value keeps the path to the Setup.exe - but without any command line options set. Also the properties before the reboot are saved in the registry under HKCU\Software\Microsoft\Windows\CurrentVersion\%IS_PREREQUF%-My Product Name In order to do an effective resume I would expect some command line options like "Setup.exe /v" "". So everything would be there - but is just not used. Writing an own registry key is not possible since it would get overwritten. I already contacted the Flexera support but they did not come up with a propper solution yet. Has anyone an idea? Thank you! ... View more