Re: [WiX-users] Heat produces invalid wxs

2007-01-04 Thread Johan Appelgren
Okey. I'll see if I can find the bug then and append to it. Thanks. /Johan On 1/4/07, Rob Mensching <[EMAIL PROTECTED]> wrote: > It's a bug in heat. There was a discussion about heat not quite getting all > the registry keys right earlier and I think a bug is opened on it (you could > add this

Re: [WiX-users] Heat produces invalid wxs

2007-01-04 Thread Rob Mensching
It's a bug in heat. There was a discussion about heat not quite getting all the registry keys right earlier and I think a bug is opened on it (you could add this information to that bug if it is missing). Unfortunately, no one is working on heat right now (since Derek left).mailto:[EMAIL PROTE

Re: [WiX-users] Heat produces invalid wxs

2007-01-04 Thread Johan Appelgren
Forgot to mention that I tested this using heat that comes with wix 3.0.2420.0 /Johan On 1/4/07, Johan Appelgren <[EMAIL PROTECTED]> wrote: > Hi, > > I ran heat on a COM dll and it produced invalid wxs xml. It looks like > it was because of a copy/paste error in a COM objects registry > settings.

[WiX-users] Heat produces invalid wxs

2007-01-04 Thread Johan Appelgren
Hi, I ran heat on a COM dll and it produced invalid wxs xml. It looks like it was because of a copy/paste error in a COM objects registry settings. The CurVer keys value was set to the progid of another COM objects progid. This caused heat to generate a class element with two progid children. Wou