That found the problem. Thanks Bob! And Phil...
It certainly is related to the scheduling of RemoveExistingProducts which I
have after InstallValidate.
One of the files had a version of 2.0.0.0 before the May 2 daily build, then
in the May 3 daily build, the version of this file was 0.0.0.0, which is
very weird. Apparently, the 2.0.0.0 file was removed (it *was* a major
upgrade) but the newer file had a lower version so it was not written.
Thanks for the attention.
On 5/9/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
John Lalande wrote:
> I have an issue where my current build on first start does a Repair if
> it has upgraded a previous version. This does not occur with a fresh
> install, only after the major upgrade.
>
> I have logged the install of the old version, the upgrade and the
> Repair, but I don't know what I should be looking for as the logs are
> very verbose.
Check the OS event log -- it records when MSI kicks in autorepair and
the reason.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
