installshield

I've been shoved into a DevOps position at work with very little knowledge about InstallShield or what I'm doing. Everything I've learned I've learned by doing and reading Flexera's documentation. One of our tickets is a problem that I haven't been able to find results for when Googling - I'm probably using the wrong search terms, but don't know what the right ones are. Basically, our installer has a buttload of features. Some of these features have sub-features, which are always installed if you select the main feature. Everything is set to be installed by default, but you can disable any of

How do I avoid distributing sensitive information in my WiX / MSI by accident? I distributed a password, machine name or login credentials by accident with my MSI file. How do I best deal with this problem? After deployment my application connects erronously to my QA / UAT systems instead of my production systems - because of a faulty debugging construct in my setup's custom action code. How can I detect and avoid this? How do I avoid distribution such information in general? This is a Q/A-style question with the simplest possible approach to avoid spreading sensitive information via your MSI

I'm finding that when I update the manifest for my bootstrapper to support Windows 10 compatability, the InstallUISequence of the MSI will correctly set VersionNT=1000, but the InstallExecuteSequence will set VersionNT=603. How do I make the InstallExecuteSequence also set VersionNT=1000? Here's my two cents.... I don't find the VersionNT property terribly useful. VersionNT64 is: VersionNT64 .... Not VersionNT64 to determine bitness. This is a bit of a hack (they do this, we do that...) but desperate times call for desperate measures.... In all of the compatibility games MSFT is playing they

I have built an Installshield installer successfully..and it is up and running..But I am a few customization away from perfection . While asking for administrative privilages in the course of installation..The permission seeking Dialog box shows weird message .which is unpleasant to anyone .I am attaching the screenshot below.. As I am new to Installshield Premier edition..can anyone please help me out with this- how can I change the pointed string AND ALSO the publisher name from unknown to my name(if possible)? UAC Prompt : " If you Authenticode-sign your .msi package, Windows will show that

I'm sure this is fairly easy, but I've kind of had a hard time with it. I've got a custom action that executes a different (non-msi) installer on installation. Unfortunately, I've noticed that it also executes the installer on UNinstallation! I've looked through the options but I cant' seem to find out how to stop this. If anybody could help me I would be incredibly grateful. Also, how do I set a custom action to go off only during UNinstall? Any help is greatly appreciated guys! saschabeaumont Add a condition on the action so it's only triggered during installation, not uninstallation. Action

Have requirement to detect windows 10 or greater version on install time. for that I have create following function. It gives me 603 (AS VersionNT value) in windows 10 and windows 8.1. That is wrong. Is there any other way to achieve this? function BOOL isWindows10OrGreater() STRING svWindowsValue; NUMBER nWindowsValue; NUMBER nBuffer; begin try nBuffer = 256; MsiGetProperty(ISMSI_HANDLE,"VersionNT",svWindowsValue,nBuffer); StrToNum(nWindowsValue,svWindowsValue); return (nWindowsValue >= 603); catch return FALSE; endcatch; end; Windows 10 - A Version Oddity Disclaimer : this information is to