I am getting some very odd behaviour when trying to test upgrading my product.
Up until now I've just uninstalled the previous version before installing the new version. But now I'm trying to actually upgrade, and what I'm getting is a little bit baffling. Just to test the upgrade, I'm only changing my .wxs file (and my executable's assembly version) and then remaking my msi. I have it so that I can install one version of my package, then change the version in the .wxs file, rebuild the msi and install that. All seemed well at first. Then I realized that I had BOTH versions of my package in the ARP list - and it seems that the install system was using reference counting on the files because they didn't disappear until both ARP versions were removed. What I WANT to happen is that the old version gets removed and the new version is installed in it's place. I realize that this is where UpgradeCode comes in, and also http://www.tramontana.co.hu/wix/lesson4.php . What I don't understand is the actual meaning of the upgrade code. Is the upgrade code meant to stay the same between versions, so that the installer knows what it's upgrading? Or is it supposed to be different, so it knows that there is some kind of change? I can't find documents actually explaining what these tags and attributes mean and how they relate, just a tutorial that talks about one particular use of them. And the tutorial actually makes it a little more confusing - I had assumed that if older versions of the same product existed I could say to remove those, but I have to list them explicitly? -- Regards, cf ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
