ssage-
From: Dana Gutride [mailto:[EMAIL PROTECTED]
Sent: Friday, 26 September 2008 3:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SQL scripts and Upgrades
Yeah, we decided that upgrading our database needs to be a linear
operation for now. If you
a Major Upgrade?
>
> Michael
>
>
>
> From: Dana Gutride [mailto:[EMAIL PROTECTED]
> Sent: Fri 26/09/2008 12:12 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] SQL scripts and Upgrades
>
>
>
>
Dana,
Are you always using a Major Upgrade?
Michael
From: Dana Gutride [mailto:[EMAIL PROTECTED]
Sent: Fri 26/09/2008 12:12 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SQL scripts and Upgrades
We just use a simple
We just use a simple version number stored in a table in the db. We read it
on upgrade using a custom action scheduled before CostInitialize and then
only components which are greater than that version number are installed
based on a component condition like what's below.
AND
--3 is the version
Hi Eitan,
I also would be interested in knowing what people are doing here.
We do something akin to yours, but have put the logic in the database
itself. We build an "update package" which is a set of database
changes. Each update package is given a GUID and as we apply the change
package we w
5 matches
Mail list logo
