Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-22 Thread Bob Arnson
Karim MacDonald wrote: > I may see if I can fix this particular bug on my own system. I don't know > how patch submissions work, but naively expect that I might then be able to > submit a patch for inclusion at some date? > Sure. You'd need to submit an assignment agreement to get it included;

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-17 Thread Karthik Krishnan
Yeah, you're right. I wrote something that autogenerated Id's as a fix to get my test build working, but my coworker, who had to use it in his project, ended up using "regasm /regfile" to generate the right entries. On 10/17/07, Karim MacDonald <[EMAIL PROTECTED]> wrote: > > > > Karthik wrote: > >

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-17 Thread Karim MacDonald
Karthik wrote: > > The problem is that autogenerated Id is not unique. It should be simple to > write a temporary postprocessor that goes through and adds Id="[unique > value]" to each RegistryValue element. > Thank you for your reply Karthik. I don't think this is the problem, as each generate

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-17 Thread Karim MacDonald
Bob Arnson-6 wrote: > > Karim MacDonald wrote: >>> would replace the element, or if this particular Heat bug (think >>> I >>> saw it logged but can't find it now!) is likely to be fixed any time >>> soon? > > So far, nobody's volunteered to maintain Heat so the bug isn't likely to > fixed soo

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-16 Thread Bob Arnson
Karim MacDonald wrote: >> would replace the element, or if this particular Heat bug (think I >> saw it logged but can't find it now!) is likely to be fixed any time soon? >> So far, nobody's volunteered to maintain Heat so the bug isn't likely to fixed soon. > I've no idea which of these i

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-16 Thread Karim MacDonald
Karim MacDonald wrote: > > > Eric Hybner wrote: >> >> Thanks Bob. FWIW, the problem appears to be with a default value. >> Removing the following registry value gets me past the issue for now. >> >> > Key="CLSID\{01D6FA3C-BCF4-35AB-820A-49ACAF99F5F8}\InprocServer32" >> Value="mscoree.dll" Typ

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2007-10-16 Thread Karim MacDonald
Hello, Eric Hybner wrote: > > Thanks Bob. FWIW, the problem appears to be with a default value. > Removing the following registry value gets me past the issue for now. > > Key="CLSID\{01D6FA3C-BCF4-35AB-820A-49ACAF99F5F8}\InprocServer32" > Value="mscoree.dll" Type="string" Action="write" /> >

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2006-12-13 Thread Eric Hybner
Thanks Bob. FWIW, the problem appears to be with a default value. Removing the following registry value gets me past the issue for now. C:\projects\sandbox\COMTest.wxs(19) : error LGHT0130 : The primary key 'reg9D78D592D2980BC3F33101F91D853AE6' is duplicated in table 'Registry'. Pleas

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2006-12-13 Thread Bob Arnson
Eric Hybner wrote: Candle yells at me because the Class/@Server attribute is missing. Please enter a bug on this -- heat should, of course, generate authoring that follows the schema. C:\projects\sandbox\COMTest.wxs(19) : error LGHT0130 : The primary key 'reg9D78D592D2980BC3F33101F91D853A

[WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

2006-12-13 Thread Eric Hybner
I heat'ed some files, and got something like this: Candle yells at me because the Class/@Server attribute is missing. I get around that by either making Class a child of the File element