Drag and Drop the field "Checked" to the list heading ... View more

duddelar wrote: Hi Stefan Thanks for the reply. You mean installation folder for placing xml files shud be different? Thanks & Rgds, Ravi. Short information: The directories 'C:\Program Files' and 'C:\Program Files (x86)' are protected from the operating system. Only Setups with elevated rights are allowed to copy or change files in this two directories. If your XML file has to be changed from your program then it schould be placed in c:\programdata\ \ " or if it depends on the the user context you should use C:\Users\%Username%\ \ ... View more

Solutions 1: Start your application with admin rights. (not a good idea) 2. Change your program. Files like XML the application have to change should be stored in something like c:\programdata\ \ ... View more

With the professional licence you can use the "InstallShield Standalone Build" in the virtual machine for "on change" compiling and use the professional licence on your PC for changing the setup script. see https://media.flexerasoftware.com/documents/Datasheet-IS2016-Compare-Editions.pdf and InstallShield Standalone Build ... View more

I changed the signature settings to: the first line for SHA1 and the second line for SHA256 http://helpnet.flexerasoftware.com/installshield23helplib/helplibrary/whats_newIS2016.htm Digital Signature Updates Beginning with InstallShield 2015, support was added to enable you to use digital certificates that use the SHA-256 hashing algorithm for signing your installations and files at build time. In InstallShield 2016, support for SHA-256 digital certificates has been enhanced for Windows Installer and InstallScript projects to: • Give you the ability to specify a digest type using the new Signature Digest drop-down on the Certificate Selection Dialog Box • RFC3161 timestamping is now supported and can be specified in settings.xml, noting that: • DigitalSignature/@Timestamp can be an Authenticode or RFC3161 server for .msi, .exe, and .dll files • DigitalSignature/@TimestampRFC3161 used for UWP app package files must be an RFC3161 server ... View more

Hi, I think it is not possible, take a look at: concurrent-licensing "•The minimum purchase quantity of concurrent InstallShield and InstallAnywhere licenses is 3 user concurrent licenses." ... View more

Take a look at https://community.flexerasoftware.com/showthread.php?217651-Installshield-2013-activation-failing-with-50040-error-amp-no-response-from-Flexera&highlight=tsconfig ... View more

Set the Registry-key for the Publisher information with installscript . (RegDBSetItem or RegDBSetKeyValueEx) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{#GUIDE#} -> Publisher ... View more

Open the 'String Editor' and search for "ID_STRING44" If the string in Value looks like 'abcdefghik' then change it to 'abcdef~1|abcdefghik' ... View more

Take look at: https://community.flexerasoftware.com/showthread.php?217651-Installshield-2013-activation-failing-with-50040-error-amp-no-response-from-Flexera ... View more

Take a look at http://helpnet.flexerasoftware.com/installshield22helplib/helplibrary/whats_newIS2015.htm Support for Windows 10–Based Systems InstallShield has support for Windows 10. Targeting Windows 10 On systems with Windows 10, the Windows Installer properties VersionNT and VersionNT64 indicate 603, which was originally introduced as the version number of Windows 8.1. Therefore, it is not possible to create conditions in an .msi package that specifically target Windows 10. Since Windows Installer 5.0 and Windows 7, DLL custom actions in .msi packages are shimmed to block obtaining the operating system version; the APIs GetVersion, GetVersionEx, and RtlGetVersion return a Windows version of 6.0.6000, which was originally the version number of Windows Vista. Therefore, it is also not possible to obtain the actual version number of Windows from a DLL custom action or from an InstallScript custom action (which is implemented as a DLL). Because of the aforementioned behavior in Windows Installer, it is not easily possible to detect what version of Windows on which an .msi package is running. In areas where you can specify target system OS requirements, such as the Installation Requirements page in the Project Assistant of Basic MSI and InstallScript MSI projects, the Windows 8.1 option has been renamed as Windows 8.1 or Windows 10 to reflect the new run-time behavior. To dedect windows 10 check the registry values: (HKEY_LOCAL_MACHINE, "SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion", "CurrentMajorVersionNumber") (HKEY_LOCAL_MACHINE, "SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion", "CurrentMinorVersionNumber") ... View more

unzip and copy the file into the directory C:\Program Files (x86)\InstallShield\2015\Searches A new predefined search should be available to check Adobe Acrobat Reader DC ... View more

No. The antivirus program notice there is a new file. Opens the file for checks (this is the time the file is blocked). After the check the file is accessible for other programs (installer) or removed (worst case). ... View more

Maybe an antivirus program blocks the access to this file. ... View more

Are you working with IS2015 Service Pack 1? I cannot reproduce the problem using the actual Service Pack. ... View more