So in a minor upgrade scenario if the component directory is and it already exists then the files will never be updated. If you do not specify a key file then the component directory is used to evaluate if the file should be upgraded. The MSI engine uses the version of the key file associated with a component to determine if the file should be replaced during a minor upgrade. The only thing that I can think of that can happen in your scenario is that the key file association for components did not get setup correctly. Just search for 'voicewarmup msi logging' in google for examples of the policy key to set. You also can set msi logging parameters in the registry.
If it has sensitive data make sure you remove that first. If you have the log file then try parsing through the output or place here if appropriate as a zip file. This is usually used so that you can create patch packages for an existing setup.Ĭhristopher was trying to help you figure out how to create a MSI log file that will list all of the actions taken when upgrading. Based on what you wrote, you are currently configured for a minor upgrade. If you want this to be a major upgrade then you do want to change your ProductCode GUID. Phil asks in his comment if you intended this to be a major upgrade. MSDN has great documentation on the difference between these two. One of the things to consider is the difference between a minor and major upgrade. $strFile = “C:InstallShield 2011 ProjectsMY 64 bit Project.Hopefully you have found a solution to the problem by now.
This example illustrates iterating through root-level features and components.
$m_Component.RemoteInstallation = $rfsSource $m_Feature = $m_(“MyApplication”)įoreach ($m_Component in $m_Feature.ISWiComponents) $strFile = “C:InstallShield 2011 ProjectsMY 64 bit Project.ism” $m_ISWiProj = new-object -comobject IswiAuto17.ISWiProject New-Variable -Option constant -Name rfsOptional -Value 2 New-Variable -Option constant -Name rfsSource -Value 1 New-Variable -Option constant -Name rfsLocal -Value 0 This example illustrates getting a specific feature from the ISWiFeatures collection, and using it to set component properties, and then saving the project. Notable differences are how the Const/Enum’s are handled, using the New-Variable scriptlet to make a read-only variable, as well as the usage of the Item function call. This time, we’re looking at Powershell, which is mostly the same story as previous efforts with other scripting engines.
0 kommentar(er)
