In the IDE, navigate to your Releases view Right click on your Release name Select Release Wizard Navigate through the panes until you come to 'Media Type' Change the Media Type to 'Network Image' Continue and save changes. ... View more

https://docs.microsoft.com/en-us/windows/desktop/msi/msihiddenproperties If you know the property name that will contain values that should be hidden in the log file then set the property to be hidden. You can find MsiHiddenProperties in the direct editor. Just append your property name to this list. ... View more

I have done this in my Suite package using InstallScript. The code below can be modified to work with MSI. In this code I implement a generalized logging method that simply calls SuiteLogInfo, but you can call SprintfMsiLog instead. This code snippet is part of a method where I pass in the element name and get its value. I do not have code to get XML attributes. szFile = szSourceFilePath ^ "mysourceFile.xml"; SuiteLogInfo("Searching for xml value in %s", szFile); if (Is(FILE_EXISTS, szFile)) then //Open file for read permission try OpenFileMode(FILE_MODE_NORMAL); if (OpenFile(nvFileHandle, szInstallPath, "systemsettings.xml") < 0) then Err.Raise(ERROR_OPEN_FAILED); endif; while (GetLine(nvFileHandle, svLine) == 0) //GetValueIfFound SuiteLogInfo("Searching for %s in line: %s", p_szName, svLine); if (StrFindEx(svLine, p_szName, 0) >= 0) then //Trim leading spaces StrTrim(svLine); SuiteLogInfo("INFORMATION: Found value for %s in systemsettings.xml", p_szName); posStart = StrFindEx(svLine,">",0) + 1; posEnd = StrFindEx(svLine, " SuiteLogInfo("INFORMATION: grabbing value between position %d and %d",posStart, posEnd); StrSub(svValue, svLine, posStart, posEnd-posStart); return svValue; endif; endwhile; catch /* Exception handler */ SuiteLogInfo("WARNING: Unable to obtain information for %s from systemsettings.xml", p_szName); endcatch; ... View more

If I am understand your problem correctly and your desired outcome, modify the release settings to make this a network image instead of a CD image. ... View more

Just from experience I would suspect that using a fast SSD such as Samsung 970 NVMe would help. For us building the file table tends to take the most time, that and compressing the package into CAB files and finally into the .EXE we distribute. When we switched from mechanical HHD to SSD we knocked significant time from our build time and we are still using old hardware that only supports 3Gb/s transfer rates. If your build system supports the NVMe format that is what I would go with today. ... View more

I have figured out the solution. My custom action now tests to see if this is a silent install by getting the property ISSilentInstall and if the value is true, then I can execute the code to validate and return an error if the command line supplied license key isn't valid. I still scheduled the event to run in OnStaging. ... View more

Here is how I handle Feature conditions: Install Level = 0 //Disabled by default [Condition: Level = 3, ISVALUE ~= "yes" Install Level = 3 //Enabled by default Condition: Level = 0, ISVALUE ~!="yes" The tilde character, '~', is to do a case insensitive comparison It seems as if you do a similar type of thing. One thing to double check is the value of INSTALLLEVEL property in the MSI log file. Is this property 200 when you run the install? Remember, INSTALLLEVEL property defaults to 1. Also, ADDLOCAL=ALL overrides INSTALLLEVEL and installs all features locally regardless of the value of the INSTALLLEVEL propety. If the value of the Level column in the Feature table is 0, that feature is not installed and not displayed in the UI. A feature is installed only if the feature level value is less than or equal to the current install level. ... View more

Webfreak, I am assuming that you are talking about the .PRQ files that we use with .MSI and .ISSUITE packages. Yes, you simply add additional OS requirements. There are cases where this can be rather tricky because of service packs for Vista and Windows 7. I thought there was a way to specify support for let's say windows 8.1 and newer but I don't see how to do that now and I could be confusing this with some other type of install element. I know I can do this with InstallShield Suite packages. ... View more

nshore, The error code just indicates a generic fatal error. You have not provided any log files, or indication of what you have done. What type of install is this? Is it a basic MSI, InstallScript MSI, etc. If .NET framework is failing to install, have you check the temp directory to see if there are log files generated there? Since you require .NET Framework, how do you have Microsoft's .NET Framework install included in your Installer? For some operating systems you will need to run DISM to enable .NET Framework, while for other operating systems you will need to download and install files from Microsoft. ... View more

intelsath wrote: Hello I have an application that need administrator privileges to run. After install it, I need check " Run this program as an administrator" in Compatibility section at Properties on shortcut icon of my program. How can I get that my program get administrative privileges using instalshield?? I may be misunderstanding your question, but if you have an application that you install must be run as administrator then you should look at including a manifest file for your application. https://docs.microsoft.com/en-us/windows/desktop/sbscs/application-manifests ... View more

If you know the URL at build time, one option is to modify your .issuite file and replace the package Url value with the correct value. The .issuite file is a simple xml file that you can manipulate just before you compile. ... View more

Unfortunately you cannot execute two MSI installs simultaneously. Have you tried scheduling the uninstall as a deferred custom action? I haven't tried this personally, but that is the first idea that comes to mind. ... View more

You do not state what type of project you are using, I will assume MSI. You will set up your component A with Destination PathA. This is very straight forward and it sounds like you already have this configured. With ComponentA visible in the IDE, expand the tree view for the component. Expand the tree view for Advanced Settings And Finally, Expand the tree view for Other Data Look to the work panel in your IDE - you should see 'DuplicateFile', click this. This takes you to Direct Editor view and to the DuplicateFile table. You will need to create an entry for each target directory and each file. See MSDN for details on the Duplicate File table https://msdn.microsoft.com/en-us/library/windows/desktop/aa368335(v=vs.85).aspx I have several entries in this table myself where files have to be duplicated to different directories. You will also need to setup the Directory table to include definitions for your three target directories so you can populate the DestFolder column. ... View more

If project files are upgraded, then when you opened the project files it would have created a backup of the original version. it will look something like this PROJECTNAME.### where ### represents the original version. If the project file did not require an upgrade then the renamed file will not be present. Me, I would just use source control (svn, git, Hg, etc) and revert my changes. Someone else will need to address the issue of the Standalone build compiling builds. I did find something interesting in my build system. A few days ago I realized that I have a project that is still compiling on the standalone build machine that uses IS2016 Standalone build. However, the project file was never converted and is still IS2015. So the Standalone Build has some ability to compile project files from previous versions - I don't know about newer versions though. ... View more