What you generate the GUID from? It's currently based on the *unique* *target* "path" (file or registry) of the KeyPath. A directory is so rarely unique it is useless for this purpose.
-----Original Message----- From: Ali-Akber Saifee [mailto:[email protected]] Sent: Tuesday, December 23, 2008 15:57 To: [email protected] Subject: [WiX-users] Autogenerated component GUID for Components which don't have a KeyPath child. I was working on cleaning up some of our buildscripts to ensure that the wxs source compiles out with the latest Wix v3 toolkit (im making a big jump from v 3.0.2128 -> 3.0.4813) and noticed the following Components that contain only one file - but it is not a KeyPath element , will cause a light error (LGHT230: The Component/@Guid attribut's value '*' is not valid for this component because it does not meet the criteria for having automatically generated guid.) Now this seems pretty valid since the file under the component isn't a KeyPath - *BUT* in my case, when a component does not have a keypath component, it is because it is using a CompanionFile to manage its upgrade. In this case would it not be fair to allow an autogenerated guid? ~/Ali ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
