Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Laxmi Narsimha Rao Oruganti (SQL CE)
: [WiX-users] Component Guids - Version Changes Laxmi Narsimha Rao Oruganti (SQL CE) wrote: 2)The GUID is pretty much stable (rather same) across all MSI where a fragment (locale independent) is used. However, I still think that for performance reasons, the GUID getting generated at compile

Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Bob Arnson
Laxmi Narsimha Rao Oruganti (SQL CE) wrote: *2)*The GUID is pretty much stable (rather same) across all MSI where a fragment (locale independent) is used. However, I still think that for performance reasons, the GUID getting generated at compile time is better. Don't know with whom I ca

Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Peter Marcu
Chris Ridd Sent: Saturday, October 13, 2007 11:07 AM To: wix-users@lists.sourceforge.net Cc: SQL Server CE Setup Team Subject: Re: [WiX-users] Component Guids - Version Changes On 13 Oct 2007, at 18:53, Laxmi Narsimha Rao Oruganti (SQL CE) wrote: > 2)The GUID is pretty much stable (rather sa

Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Chris Ridd
On 13 Oct 2007, at 18:53, Laxmi Narsimha Rao Oruganti (SQL CE) wrote: > 2)The GUID is pretty much stable (rather same) across all MSI > where a fragment (locale independent) is used. However, I still > think that for performance reasons, the GUID getting generated at > compile time is be

Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Laxmi Narsimha Rao Oruganti (SQL CE)
users@lists.sourceforge.net Cc: SQL Server CE Setup Team Subject: RE: [WiX-users] Component Guids - Version Changes The bit in Derek's article under Here's how it works explains how it works. It computes the full target path for the single file in the component (multiple files are not supp

Re: [WiX-users] Component Guids - Version Changes

2007-10-13 Thread Mike Dimmick
The bit in Derek's article under Here's how it works explains how it works. It computes the full target path for the single file in the component (multiple files are not supported). It then generates the GUID as a hash of the full target path. That means that as long as you don't change the target