Yes it is required:
http://blogs.msdn.com/robmen/archive/2004/12/08/278746.aspx has my guesses.
Michael Herger wrote:
> Reading the tutorial at http://www.tramontana.co.hu/wix/lesson4.php once
> again, I'm even more confused: "You have to [do a major upgrade] when you
> change the name of the .
es/.
> Neil
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com <mailto:n...@x2systems.com>
>
>
>
> From: Michael Herger [mailto:s...@herger.net]
> Sent: Tue 17/02/2009 09:53
> To: General discussion for Windows I
s/.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Michael Herger [mailto:s...@herger.net]
Sent: Tue 17/02/2009 09:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Updat
Reading the tutorial at http://www.tramontana.co.hu/wix/lesson4.php once again,
I'm even more confused: "You have to [do a major upgrade] when you change the
name of the .msi file for any reason.". But who on earth would distribute a
small update to an existing product with the same .msi file na
Hi Alexander,
thanks for your feedback. Yes, my example is not very helpful... But I've gone
through so many version and tests - I don't know what to post. The latest way
I've been testing is Neil's
(http://neilsleightholm.blogspot.com/search/label/WiX). But in this case I'd
end up with X copi
Hi Michael,
Make sure you follow all required steps to make major upgrade work. In your
simplified code I see Version attribute hard coded to "0.0.0.0". Also, you did
not provide your table and how you schedule .
It is not obvious from your code if you change Product/@Id with every build.
6 matches
Mail list logo
