I have encountered this also. This a defect in light.exe 3.0.5419, which I
confirmed by downloading the WiX 3.0.5419 source code and searching for the
error message. (I did this a few months ago, so I can't remember the exact
location off the top of my head.)
This is what the linker does in 3.0.
Not sure what the problem actually was. I scrapped what I had, and started
over. Everything working now as expected.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-Guid-error-tp7579390p7581179.html
Sent from the wix-users mailing list a
Oh, heh. Missed that pertinent part.
Uhh, I don't know how this could be happening. Is it possible this is about
a Component that doesn't have a Guid attribute at all? I'll have to try a
small experiment myself but I don't know how the code could do this.
On Thu, Jul 12, 2012 at 11:25 AM, bpack
Rob,
Unless I am mistaken, that criteria: "[no] Property substitutions ..." is
only relevant if I am asking WiX to generate the Guid; which seems to be
indicated in the initial message.
"The Component/@Guid attribute's value '*' is not valid for this
component..."
What has me confused is that th
This part of the error message is pertinent: "[no] Property substitutions
as the key path"
On Wed, Jul 11, 2012 at 12:36 PM, Bill Packard wrote:
> WiX 3.0.5419, VS 2008.
> Attempting to convert merge modules (only used internally) to wixlib.
> Almost there, but have encountered a set of errors th
WiX 3.0.5419, VS 2008.
Attempting to convert merge modules (only used internally) to wixlib. Almost
there, but have encountered a set of errors that make no sense. Example
fragment and error are below.
Source.wxs(61,0): error LGHT0230: The Component/@Gui
6 matches
Mail list logo
