Property upgrade/change problem
I'm upgrading an application to a newer version. As part of the overall upgrade several of the properties have had their values changed (e.g. Previously SERVER=WIN2000, for the new version SERVER=WIN2003).
My problem is that the upgrade is pulling the properties from the previously installed version and not changing them to the newer values.
MSI logging reports similar lines for all the properties that are requried to change.
PROPERTY CHANGE: Modifying SERVER property. Its current value is 'WIN2000'. Its new value: 'WIN2003'.
I know that I've figured this out before, but it's been a long day and I haven't packaged for a while. Thanks in advance.
Mike
My problem is that the upgrade is pulling the properties from the previously installed version and not changing them to the newer values.
MSI logging reports similar lines for all the properties that are requried to change.
PROPERTY CHANGE: Modifying SERVER property. Its current value is 'WIN2000'. Its new value: 'WIN2003'.
I know that I've figured this out before, but it's been a long day and I haven't packaged for a while. Thanks in advance.
Mike
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
My problem is that the upgrade is pulling the properties from the previously installed version and not changing them to the newer values.
PROPERTY CHANGE: Modifying SERVER property. Its current value is 'WIN2000'. Its new value: 'WIN2003'Forgive me, Mike (my excuse is that it's early morning...), but aren't these two statements mutually exclusive? Either the values are changed or they're not. Do you mean that the application is pulling old values?
Posted by:
MSIPackager
15 years ago
Posted by:
michaelnowell
15 years ago
Afraid that that's one of the first things that I checked.
I'm assuming that it's working in a similar way to how features work with upgrades. When the upgrade looks at what features are present in the installed version and then modifies the upgrade to only install those that are currently on the machine. Does that make sense?
Anyone else have any idea's as I don't really want to have to uninstall the previous application first before I install the newer version?
I'm assuming that it's working in a similar way to how features work with upgrades. When the upgrade looks at what features are present in the installed version and then modifies the upgrade to only install those that are currently on the machine. Does that make sense?
Anyone else have any idea's as I don't really want to have to uninstall the previous application first before I install the newer version?
Posted by:
michaelnowell
15 years ago
I thought that I'd worded it a little funny.
The application is pulling the old values from the installation that exists on the PC, not the values that I wish to change them to that are specified in my upgrade.
The actual line from the log is
PROPERTY CHANGE: Modifying IAAPPSERVER property. Its current value is 'CV-CRM56'. Its new value: 'CV-CRM'
Where CV-CRM is the old value and CV-CRM56 the value that I want it to be set to.
The application is pulling the old values from the installation that exists on the PC, not the values that I wish to change them to that are specified in my upgrade.
The actual line from the log is
PROPERTY CHANGE: Modifying IAAPPSERVER property. Its current value is 'CV-CRM56'. Its new value: 'CV-CRM'
Where CV-CRM is the old value and CV-CRM56 the value that I want it to be set to.
Posted by:
AngelD
15 years ago
Posted by:
michaelnowell
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.