The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click
here
for more information.
I'm trying to activate InstallShield Express 2018, and it also end up with successful activation, but InstallShield does not open after activation,and when starting again it ask for activation again?How do I proceed?-cpede
I have converted an ISX 2009 to ISX 2010 project. In this project I have a number of Custom Actions running after the Ready To Install dialog has been shown.This still works on Vista, but on 7 the Ready To Install dialog has changed, but more importa...
I have used ISX 12 to install a program. Now I have upgraded to ISX 2008 and cannot get the upgrade path to work correctly.When installing the new version it installs perfectly, even migrate features and all. But when I click on my desktop shortcut o...
When do we have a version that:1) Works for restricted users on Windows XP2) Works without repeating the installation without succeeding when other users log in3) Includes an uninstall feature for customer who don't want the Update Manager installedT...
If you create the installer with ISX 2013 on the same PC as VS 2010 exist, you can always find the merge modules for the compiler in the c:\program files\common files\merge modules folder. Using this path also ensures, that you get the correct versio...
It seems that you are trying to install your "old" application on a Windows x64 version. This is why the registry keys are installed under the Wow6432Node key, since ISX only support installing x86 applications (without Orca tweaks).All this is prob...
We also came across this. The reason is that the Product Code is the same between your builds (even you change the version number). Remember that the Upgrade Code must always be the same!I'm sure that, if you change the Product Code it will upgrade c...
