coapp-developers team mailing list archive

["Rivera, Rafael" <rafael@xxxxxxxxxxxxxxxxx>]

 Welllllllll, drivers.... never mind. /hides



On 8/12/2010 9:18 PM, Garrett Serack wrote:
>
> We're NEVER GONNA UPGRADE using MSI.
>
>  
>
> NEVER.
>
>  
>
> Windows Installer fucked this up, and we're not gonna follow.  We
> always want it physically possible to have two versions installed.
> This is the secret sauce to "No Reboots. Fucking Ever."  :D
>
>  
>
> G
>
>  
>
> *From:*
> coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx
> [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx]
> *On Behalf Of *Trevor Dennis
> *Sent:* Thursday, August 12, 2010 6:07 PM
> *To:* Rivera, Rafael
> *Cc:* coapp-developers@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Coapp-developers] Questions, Questions, Questions
>
>  
>
>  
>
> On Thu, Aug 12, 2010 at 6:50 PM, Rivera, Rafael
> <rafael@xxxxxxxxxxxxxxxxx <mailto:rafael@xxxxxxxxxxxxxxxxx>> wrote:
>
> Oh, sorry. Wow. I just fell into that GUID-being-a-real-GUID trap that
> was just talked about moments ago. Yikes.
>
> /rafael
>
>
>
> On 8/12/2010 8:49 PM, Eric Schultz wrote:
>
> Rafael,
>
>  
>
> We want to be able to provide a consistent ID for a package no matter
> how many times its built. By using the package name, version,
> architecture and the publisher's public key token, the same package
> will always have the same ID.
>
>  
>
> Eric
>
>  
>
>  I have another quick question. Are these ID's in anyway related to
> the ProductCode and UpgradeCode in the end MSI?
>
> If so, the UpgradeCode must be consistent among all versions of a
> single product.  It cannot change with the version number.  If this
> value changes, Windows cannot find the correct product to upgrade when
> installing the newer MSI for a package.  We may need a way of tracking
> this GUID and keeping it the same across releases. 
>
>  
>
> If we generate it via your hash, it should be okay as long as version
> is not included.
>
>  
>
> On the other hand, ProductCode and PackageCode must be unique on every
> new MSI update.  They could include the version, or simply be a real GUID.
>
>
> -- 
>
> Trevor Dennis
>