I am running Installshield 2014 Premier edition but i have no option to run Installshield through Visual Studio. Was Visual Studio supposed to be installed first before Installshield was installed?
I am having problems inserting a custom [PROPERTY] into the EXE Command Line area when installing an exe. i have tried "[PROPERTY]" as well as just [PROPERTY] and neither ware working for me.When configuring msi package command lines it works perfect...
I have a Suite Installation that has 4 packages(.msi) and some prerequisites in it. Installation works fine and uninstallation works fine. The problem i am having is the installer getting stuck when try to modify the already installed application.-In...
So i am working with a Basic MSI project to enable IIS features and give a progress bar back to the user. The basic MSI when run on its own, works perfectly and as expected. The problem i am having is when i add this IIS.msi package to my Suite insta...
I cant seem to figure out how to user my [MyProperty] inside of the custom method signature. I have tried [MyProperty], "[MyProperty]", "MyProperty".I have also tried the "CustomActionData" method from here with no success. Anyone have a solution?
So, what i ended up doing was 'Repairing' my current Installshield 2014 version that i currently run and now my Visual Studio integration is showing up. I think in my case that Visual Studio was installed AFTER Installshield so it obviously left out ...
Would that not defeat the purpose of UAC on the OS if an application could disable it? I think the best you can do is sign the packages so that they show your company name in the UAC dialog prompt.