Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

Upgrade table - - Strange behavior of the msi

2 replies to this topic


  • Full Members
  • 93 posts

Posted 23 April 2012 - 07:59


I recently came across a MSI which had upgrade table entries as follows:
Column Value
UpgradeCode <Upgrade Code>
VersionMin Blank or null
VersionMax Blank or null
Language Blank or null
Attributes 0(This value is not documented on MSDN)
Remove Blank or null
ActionProperty <Some GUID> (This is valid as the GUID has all uppercase characters)

From reading the MSDN documentation, it is very clear that both VersionMin and VersionMax columns cannot be null. However, in this case , both the columns had null values.
There is no documented behavior for an attribute value of 0. However, the attribute column had a value of 0 for this entry.

Inspite of all the above, the msi was able to perform a successful major upgrade.
Can anyone explain this strange behavior?

Kiran Hegde

Stefan Krueger

Stefan Krueger


  • Administrators
  • 13,269 posts

Posted 24 April 2012 - 08:49

0 for Attributes is okay. It means that none of the flags is set.

VersinMin and VersionMax both blank is not allowed per documentation, which means that the result is undetermined. It might uninstall any version (as it seems the case here), it might not uninstall any version, or it might crash.

ActionProperty must be a valid property name (not a GUID). It may contain characters, digits, underscores or periods. But no curly braces {} or hypens. So a GUID is not a valid property name (and it would also be quite confusing).


  • Full Members
  • 93 posts

Posted 24 April 2012 - 09:03

Thanks Stefan.
That sounds convincing...