The upgrade code is the same. You know, for some odd reason I was
just going to try a 3 field version instead of 4 and then you
mentioned this. My versions are like 1.0.0.1 and 1.0.0.2... I just
figured if it was smart enough to know that something had changed
(because it wasn't asking me for rep
Is the upgrade code set correctly? Generally the upgrade code should
be the static over the lifetime of your product, it's the one thing
that doesn't change between versions, builds, etc.
Also note that Windows Installer only recognizes the first three
fields of a version number for MSI packages,
Thanks for the response. I had not tried a custom action, but I did
just now. Same problem, doesn't do anything. When I go through the
logs the NEWERVERSIONDETECTED and OLDERVERSIONDETECTED properties are
not getting set. Therefore the conditions are false and the custom
action never runs. I
Have you tried using a custom action, instead of a launch condition to
block install?
e.g.
On Fri, Dec 18, 2009 at 9:44 AM, Jason T. wrote:
> Hello,
>
> I'm trying to detect when a different version of my package has
> al
Hello,
I'm trying to detect when a different version of my package has
already been installed so that I can abort the installation. I'm not
looking to do the "major upgrade", I just want to abort if either an
older or a newer version is found (if the version is the same the
repair/remove logic al
5 matches
Mail list logo
