Posted 10 February 2005 - 23:45
The problem I am having is that the files do not seem to be updated. I create an install package and install it. I then update and version the files contained in the installation package and build it again while changing the package code. I then install this new package and the files are not updated. Wasn't this suppose to be automatic? Or do I have to run this second install with the REINSTALLMODE and REINSTALL msi options? If those options are required I would like to find a way to get around it as I would rather not have our customers run the setup from the command line with these flags. I tried to put those flags in the package to be run each time, but when I do that nothing gets installed.
Posted 11 February 2005 - 09:42
Otherwise, if you really changed the package code, you would receive an error message "Another version of this product is already installed".
You can use a setup.exe launcher that will launch the msi with the appropriate parameters. Many authoting tools include such a setup.exe, or you can use one of the feee launchers listed under "Launchers and Runtime Installers" at http://www.installsi...s.htm#Launchers
Another option would be building a patch (.msp) instead of a full .msi package.
Posted 11 February 2005 - 16:46
Posted 11 February 2005 - 19:35
But you don't need to specify these parameters in InstallShield X. Remove them and instead go to Media > Upgrades > Upgrade Windows Installer Setup. In the Small/Minor Upgrade field select either "Prompt" or " Don't prompt just install the upgrade". Rebuild your release.
Posted 11 February 2005 - 23:03
My Small/Minor upgrade setting was set to Prompt. If I ran a setup that was more recent than what I had installed I would be prompted to proceed with the upgrade. That ran fine but none of the files would be updated. I could post the log file I generated when running the more recent installer if that would help.
Posted 18 February 2005 - 00:12
The Upgrade Validation you mentioned in your previous post, do you mean by right clicking the Upgrade Windows Installer Setup and selecting Validate All Items?
Posted 18 February 2005 - 18:37
The log file does not mention copying any files over when running the update. This is verified by checking the version of the file that should have been updated. The file is not updated.
Now I don't have any particular minor update items listed in the Upgrade view and other install projects that I have seem to work without that. Is there anything that you could think of that I might be missing here?
Posted 21 February 2005 - 11:26
Can you generate a verbose log file of the update install (from the test project you just described), zip it, and post it here?
Posted 23 February 2005 - 22:14
I was told I couldn't attach zip files so this is uncompressed.
Edited by scootyd, 23 February 2005 - 22:17.
Posted 25 February 2005 - 00:27
Posted 25 February 2005 - 00:28
Posted 25 February 2005 - 15:21
I think this is what you're doing? I think you may also have broken some other rules too?
If you're using MSI 3.0 (you are), could you try adding the following property to you property table or commandline: "MSIENFORCEUPGRADECOMPONENTRULES=1". I've never seen this property in action yet, so please let us know what happens!
Just for my own curiosity - is your company policy to install applications "per machine" or "per user"?
Edited by mandy, 25 February 2005 - 16:59.
Posted 02 March 2005 - 17:16
I didn't think I was using MSI 3.0. I'm using InstallShield X to develop these installers. Is this property only available in MSI 3.0? Let me know if it's available in the older MSI and I'll give it a try.
Our company policy allows a user to install this particular product on a "per machine" basis.