Confused - UpgradeCode on NET 2003 msi

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

thejamie - 16 Mar 2005 17:01 GMT

I'm confused. I have been building a net msi for over a year without any
problems arising from multiple installations appearing in the add-remove
setup. I have been careful to NEVER CHANGE THE UPGRADECODE! I wrote it on
a note and taped it to my computer.

After checking the project in, deleting the original and checking it out to
a new folder, upgrading the Crystal msm's, the project began installing with
a new reference in the add remove programs with each build (despite having
the same upgradecode as the original). After becoming frustrated, I broke
my rule and tried to start fresh and upgraded the upgrade code and told
everyone to uninstall the old product and reinstall the new.

Once again, I am not changing the upgrade code, but the issue of multiple
add-remove references has not gone away and for what I know of it, this
should have ended with the advent of a new UpgradeCode. Any help on this
would be appreciated.

Signature

Regards,
Jamie

Reply to this Message

Phil Wilson - 18 Mar 2005 17:57 GMT

VS-generated MSI files have the ALLUSERS property set to 2. This is IMO an
unfortunate choice because if you don't have admin privileges you get a
per-user install, and if you do have them you get a per-system install
(equivalent to the just me/everyone choices). This happens silently. The
point here is that a per-system upgrade will not upgrade a per-user and vice
versa, so you end up with two products on your system. That's the likely
explanation - per-user/per-system often causes this issue. If ALLUSERS was 1
in the MSI file, you'd get an error if you didn't have admin privs, so you
could think about setting it after the build.

Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

> I'm confused. I have been building a net msi for over a year without any
> problems arising from multiple installations appearing in the add-remove
[quoted text clipped - 16 lines]
> should have ended with the advent of a new UpgradeCode. Any help on this
> would be appreciated.

Reply to this Message

jamie - 19 Mar 2005 00:01 GMT

ALLUSERS=1 sounds like the right choice. Thank you

> VS-generated MSI files have the ALLUSERS property set to 2. This is IMO an
> unfortunate choice because if you don't have admin privileges you get a
[quoted text clipped - 27 lines]
>> should have ended with the advent of a new UpgradeCode. Any help on this
>> would be appreciated.

Reply to this Message

Confused - UpgradeCode on NET 2003 msi

Free Magazines