Jan 14, 2016
09:54 AM
LanceRas wrote: But I need to be able to dual sign the MSI before it is wrapped in the Setup.EXE. Details in regard to why dual sign MSI is not supported was provided by Josh Stechnij (Software Engineer - Flexera Software: InstallShield Team) in another thread. https://community.flexerasoftware.com/showthread.php?218163-Codesigning-using-SHA-2-SHA256&p=507778#post507778
... View more
Apr 26, 2011
05:45 PM
I did some additional testing and noticed if specify path(s) via the -o flag it will not also include the default locations when looking for merge modules. For example, if the project references two different merge modules (different network paths) and only included path for one via -o while relying on the default location for the other, it will fail. Though, I view that as a good thing as it ensures that will always use the merge module that is specified in one of the paths and not whatever is local since the network path may have newer build. Again, multiple build machines are involved and the MSI project may or may not be built on the same machine as the merge module(s). This answers my second question, though the first question still is valid. Can network repository be used with standalone build, if so how is the network repository path specified without the IDE? Or is the -o flag the way to go?
... View more
Apr 26, 2011
03:50 PM
Scenario: Multiple merge modules Multiple MSI projects that reference the various merge modules Multiple build machines via InstallShield Standalone When a merge module is built, it will get copied to a folder on network. The problem arises if a build of an MSI project is done on a build machine that didn't have the referenced merge module also build on same machine (no copy in the default C:\InstallShield 2011 Projects\MergeModules folder). One solution is to specify the network path via -o command line argument to ISCmdBld.exe to include additional search paths. Questions: Instead of specifying the -o flag, would it be better to use network repository (we have Premier edition)? If so, how do you specify the path to network repository within standalone since there is no IDE? Additionally, if a merge module exists in the local C:\InstallShield 2011 Projects\Merge Modules folder AND in a path specified by -o flag (or in network repository) will InstallShield automatically grab the one from network if it is newer (same version, but newer date modified timestamp) instead of taking from the local default folder?
... View more
Labels
- Labels:
-
InstallShield 2011
Mar 18, 2011
03:55 PM
For completeness, I also tested the version values regarding the Upgrade table. It does not matter if padding is used or not, the upgrade entries all work as expected. This is true even for scenarios when the installed version had padding and upgrade entry did not, and vice versa. In summary, there appears to be no problems with the short or long version strings with one exception: if you are doing your own string comparison such as an install condition (see previous post). If you think you may need to include a version in a condition, then perhaps consider padding otherwise it is pefecttly fine to use the no-padding approach.
... View more
Mar 07, 2011
01:26 PM
I did some simple testing with install condition. As expected, string comparisons require the extra padding to work properly. Otherwise "1.10.0" is treated as less than "1.9.0". As such, I'll probably always add extra padding. What are others out there doing?
... View more
Feb 16, 2011
09:32 AM
We are in similar situation where desire DirectX prerequisite instead of merge module / InstallShield object. We ultimately created our own prerequisite for the web installer available from Microsoft. Anyone else have thoughts on this topic as to best option?
... View more
Jan 11, 2011
04:31 PM
Is there a best practice for the format used with product version? Specifically, padding with zero's. For example: "4.06.0007" vs. "4.6.7" When creating a new project in InstallShield, the default value for product version is "1.00.0000". I find the extra zero's to hurt readability (think of elevated support call with user reading back version number...). Perhaps the zero's make it easier to compare versions when treating as strings.
... View more
Labels
- Labels:
-
InstallShield 2011
Dec 16, 2010
04:52 PM
It appears that the distribute after build (copy to folder) option will still run even if upgrade validation failed. It would be preferred to NOT distribute to the specified folder in cases of errors during upgrade validation. Warnings would be acceptable to distribute after build, for most part. Is this configureable? Any other thoughts?
... View more
Labels
- Labels:
-
InstallShield 2011
Dec 10, 2010
07:37 PM
Thanks for the suggestion. Though I am not sure that will work in all cases. In particular, the scenario of a major upgrade of one of the products while another product(s) was also found. Still would want RemoveExistingProducts to execute in order to remove the currently updating product. RemoveExistingProducts action only runs once and not once for each product to uninstall, so I don't think that adding condition would help. (I could be wrong, but those are my initial thoughts). Taking a step back, the MSDN documentation for RemoveExistingProducts action: The RemoveExistingProducts action goes through the product codes listed in the ActionProperty column of the Upgrade table and removes the products in sequence by invoking concurrent installations. That may be the answer. I could conditionally clear the respective property that should not be uninstalled after FindRelatedProducts but before RemoveExistingProducts. All in all, I think it would be much preferred to have the ability at build time to include/exclude major upgrade items accordingly instead of these extra steps. Thoughts on this feature request? Or maybe it is rare to have related products within same installer project that ultimately need to be treated as unrelated?
... View more
Dec 09, 2010
10:38 AM
Windows Installer will cache the MSI tables within a system folder so it can perform uninstalls accordingly. However, none of the binaries are cached meaning cannot perform maintenance unless browse to the install media or it is cached on the target computer. I believe you are referring to the setting in the Setup.exe tab under Releases view within InstallShield. Note that it will only be enabled for relases that do not have the msi file available in the same folder as the setup.exe - for example a compressed build where the only output is a single setup.exe. Specifically, the help says it will: Cache the .msi file and other installation files on the target system for use with application maintenance and repair. The default location is [LocalAppDataFolder]Downloaded Installations\ . On a Windows XP it will be C:\Documents and Settings\ \Local Settings\Application Data\Downloaded Installations\ and on Windows 7 it will be C:\Users\ \AppData\Local\Downloaded Installations\ . Generally I will modify that path to also include our company and product name. I have follow-up question to others in the community. When are these cached msi's deleted? They appear to remain even after uninstalling. Additionally, since package code changes for every build (configurable within InstallShield) there will be many cached msi's if many installs occur. For frequent large installations this can add up to several gigabytes over time.
... View more
Dec 08, 2010
03:52 PM
Thank you for the feedback, including the link to Microsoft's documentation for further understanding. I named my shortcut "IS 2011" and it works great. Thanks again.
... View more
Dec 07, 2010
05:49 PM
I have a single InstallShield project that contains multiple product configurations. They are related products in that some of them share common features, components, and custom actions directly instead of going through a merge module layer. Product flags are then used in conditions to include or exclude according to the product configuration being built. This has been working well except one small issue. There is no way to include/exclude major upgrade items based on product configurations. As such, if two products from the same installer project are installed on the same computer then a major upgrade to one will also remove the other product even though they have different upgrade codes. This could be resolved by having ability to include/exclude major upgrade items to specific product configurations at build time. Would this feature request be of value for others also?
... View more
Labels
- Labels:
-
InstallShield 2011
Dec 07, 2010
04:31 PM
Is anyone else having difficulties pinning InstallShield 2011 to the Windows 7 taskbar? I am referring to the InstallShield 2011 product itself and not any installation created from it. For some reason I am unable to do so. It doesn't matter if I create a shortcut first or directly try to drag isdev.exe to the taskbar. I do not have the taskbar locked and I am able to drag other shortcuts and applications without any issues.
... View more
Labels
- Labels:
-
InstallShield 2011
Feb 11, 2010
03:32 PM
I found an additional thread that discusses IS_MINOR_UPGRADE http://community.flexerasoftware.com/showthread.php?t=138411
... View more
Feb 11, 2010
03:27 PM
Conditional Statement Syntax http://msdn.microsoft.com/en-us/library/aa368012.aspx I have some custom actions with a condition to run when a certain feature is installed. &FeatureName=3 That works great with first time installs and major upgrades. However, I would also like the custom action to run during minor upgrades when that feature is being updated (newer files). My initial thought was that the feature's action would be INSTALLSTATE_LOCAL for minor upgrades also. However, looking at the log it shows as re-install. [FONT="Courier New"]MSI (s) (B0:C4) [14:10:35:562]: Feature: FeatureName; Installed: Local; Request: Reinstall; Action: Reinstall[/FONT] As such, the custom action does not run during minor upgrade. I then modified my condition to handle minor upgrades and maintenance repairs. (&FeatureName=3) OR (!FeatureName=3 AND (REINSTALL="ALL" OR REINSTALL><"FeatureName")) The above works great. I guess this forum post is less of question and more of a knowledge share in case others had similar scenario. I was also wondering if anyone could shed some additional light on the IS_MINOR_UPGRADE property. I can't seem to find any documentation on the property in InstallShield help or in MSDN for Windows Installer. Perhaps another option would be to use: (&FeatureName=3) OR (!FeatureName=3 AND IS_MINOR_UPGRADE)
... View more
Labels
- Labels:
-
InstallShield 2010
Latest posts by AaronM
Subject | Views | Posted |
---|---|---|
647 | Jan 14, 2016 09:54 AM | |
624 | Apr 26, 2011 05:45 PM | |
3130 | Apr 26, 2011 03:50 PM | |
870 | Mar 18, 2011 03:55 PM | |
870 | Mar 07, 2011 01:26 PM | |
394 | Feb 16, 2011 09:32 AM | |
3105 | Jan 11, 2011 04:31 PM | |
1584 | Dec 16, 2010 04:52 PM | |
606 | Dec 10, 2010 07:37 PM | |
1035 | Dec 09, 2010 10:38 AM |
Activity Feed
- Posted Re: Dual Code Signatures on InstallShield Forum. Jan 14, 2016 09:54 AM
- Posted Re: Merge Modules and Standalone Build (ISCmdBld.exe) on InstallShield Forum. Apr 26, 2011 05:45 PM
- Posted Merge Modules and Standalone Build (ISCmdBld.exe) on InstallShield Forum. Apr 26, 2011 03:50 PM
- Posted Re: Format for product version on InstallShield Forum. Mar 18, 2011 03:55 PM
- Posted Re: Format for product version on InstallShield Forum. Mar 07, 2011 01:26 PM
- Posted Re: DirectX web-installation on InstallShield Forum. Feb 16, 2011 09:32 AM
- Posted Format for product version on InstallShield Forum. Jan 11, 2011 04:31 PM
- Posted Disable distribute after build when upgrade validation fails on InstallShield Forum. Dec 16, 2010 04:52 PM
- Posted Re: Include/exclude major upgrade item based on product configuration on InstallShield Forum. Dec 10, 2010 07:37 PM
- Posted Re: How to cache the .msi for maintenance on InstallShield Forum. Dec 09, 2010 10:38 AM
- Posted Re: Unable to pin InstallShield 2011 to Windows 7 taskbar on InstallShield Forum. Dec 08, 2010 03:52 PM
- Posted Include/exclude major upgrade item based on product configuration on InstallShield Forum. Dec 07, 2010 05:49 PM
- Posted Unable to pin InstallShield 2011 to Windows 7 taskbar on InstallShield Forum. Dec 07, 2010 04:31 PM
- Posted Re: Condition for custom action during minor upgrade on InstallShield Forum. Feb 11, 2010 03:32 PM
- Posted Condition for custom action during minor upgrade on InstallShield Forum. Feb 11, 2010 03:27 PM
- Posted Re: Using feature prerequisites in silent mode on InstallShield Forum. Oct 07, 2009 11:57 AM
- Posted Re: Using feature prerequisites in silent mode on InstallShield Forum. Oct 07, 2009 11:40 AM
- Posted Re: Feature prerequisite with release flags causes install to fail on InstallShield Forum. Sep 01, 2009 12:08 PM
- Posted Feature prerequisite with release flags causes install to fail on InstallShield Forum. Aug 31, 2009 02:27 PM
- Posted Re: Changes to how product configuration and release flags are handled in 2010 on InstallShield Forum. Aug 27, 2009 02:22 PM