the "How To: Generate a GUID" document (excerpt below) suggests that wix 
supports compiling with PUT-GUID-HERE tokens vs actual Guid values or where 
allowed "*" token autogenerated Guid values defined...but the PUT-GUID-HERE 
tokens case isn't working with the latest install

"All examples in the How To documentation use the text 
PUT-GUID-HERE<mk:@MSITStore:C:\Program%20Files%20(x86)\Windows%20Installer%20XML%20v3\doc\WiX.chm::/html/generate_guids.htm>
 for GUIDs. These samples can be compiled directly by WiX and will have 
temporary, auto-generated GUIDs, inserted. For production purposes you should 
replace each occurrence of 
PUT-GUID-HERE<mk:@MSITStore:C:\Program%20Files%20(x86)\Windows%20Installer%20XML%20v3\doc\WiX.chm::/html/generate_guids.htm>
 with an actual GUID generated using the methods described above."

We are trying to maintain a service deliverable template setup.wixproj and so I 
want to use PUT-GUID-HERE tokens wherever a Guid is required so users of the 
template will ultimately be required to use their own unique guids or where 
allowed "*" token autogenerated Guid values.    When I compile with the 
PUT-GUID-HERE tokens in place I get the following compiler error.

"The Product/@Id attribute's value, 'PUT-GUID-HERE', is not a legal Guid value. 
 A Guid needs to be generated and put in place of 'PUT-GUID-HERE' in the source 
file.        "

Question - am I misinterpreting the documentation or am I using the 
template/sample oriented guid token PUT-GUID-HERE incorrectly?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to