Why not just write the information you require in the registry and store it
in a public property in each MSI.

That way you can generate your product code as normal and run no risks of
current or future problems with not following the guidelines for GUID
generation.

You can even make it more human readable than packing things into a pretend
guid.




-----Original Message-----
From: Aaron Klor [mailto:aaron.k...@gmail.com] 
Sent: 09 May 2011 15:06
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] [Wix-users]

We are considering defining our product codes for our different instances
with a bit more structure than the random GUID generation that is usually
recommended. We are considering this because we have to define a large
number of product code GUIDs for each product AND change them every time we
do a build. There is precedent for this sort of behavior (set by the
Micrsoft Office team, see
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\90140000-XXXX-XXXX-0
000000FF1CE),
so we've decided to ask the list in order to hopefully gain some insight as
to whether this is considered "bad form" or if this might be acceptable.


For reference, we were considering something of this form:

{XXXXXXXX-XXXX-XXXX-CoPr-MaMiRvBildIn}

Where the X's are randomly generated GUID bits, but will be the same
throughout our products

The description of the rest of the fields are:

Co:  8-bit company code (human-readable, using A-F)

Pr:   8-bit product code (human-readable, using A-F)

Ma:  Major rev

Mi:   Minor rev

Rv:   Revision

Bild: Build number

In:    Instance number


We understand that this significantly reduces the randomness of the GUID
(potentially removing the GU part of GUID), but given the manageability
gains, we feel that it might be worth it. It gives us the ability to easily
generate (and programmatically search for) up to 255 instances, allows for
revisions up to 255.255.255.65535, and can potentially simplify our WiX
authoring.


Obviously, this will cause problems in the case a GUID collision occurs
between our product and someone else's, but we find this highly unlikely
given that there are still 64 random bits in the GUID. I suppose the real
question is: is there something that we're missing? Might this sort of thing
affect things outside the ARP on Windows machines?


Thank you for your help,

Aaron Klor
-----------------------------------------------------------------------------
-
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to