Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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; see http://blogs.msdn.com/robmen/archive/2004/04/14/112970.aspx for details. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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: > > > > 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 > generated Id seems to be unique to a given registry path+value. This seems > sensible, as you wouldn't normally want to be writing from the reg-table > to > the same reg-value twice in the same setup. > -- > View this message in context: > http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250236 > Sent from the wix-users mailing list archive at Nabble.com. > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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 generated Id seems to be unique to a given registry path+value. This seems sensible, as you wouldn't normally want to be writing from the reg-table to the same reg-value twice in the same setup. -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250236 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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 soon. > 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? Bob Arnson-6 wrote: > > Both are bad because they violate component rules. > Could you be more specific about which rules they break please Bob? I've checked MSDN and although the same registry value is being written to twice, I can't see a component rule problem as long as this all happens within one component. Bob Arnson-6 wrote: > > Is it not enough to remove the mscoree.dll InprocServer32 value? > Unfortunately the mscoree.dll value is correct & not the problem: it's needed so that COM knows to prod .NET when the object is CoCreated. The root problem (I think) is that Heat is wrongly guessing the content of that registry value when it doesn't need to. A clean work-around would be a short dark.exe segue and then ditch the element from the authored code (I might do this). -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250119 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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 is better or worse; comments gratefully > received... > Both are bad because they violate component rules. Is it not enough to remove the mscoree.dll InprocServer32 value? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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" Type="string" Action="write" />
>>
>
> Does anyone know if there is a workaround to this problem that is better
> than manually writing all of the appropriate elements that
> 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?
>
Found a couple of alternatives, neither of them nice:
1. Give a unique Id to the mscoree RegistryValue (which will result in the
value being overwritten by two separate Registry table entries):
2. Advertise the component (=> the reg-entries will be written by the
RegisterClassInfo action I think) and then forcefully zero its Darwin
descriptor (WriteRegistryValues occurs after RegisterClassInfo by default):
...
I've no idea which of these is better or worse; comments gratefully
received...
--
View this message in context:
http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13239912
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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" />
>
Does anyone know if there is a workaround to this problem that is better
than manually writing all of the appropriate elements that
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?
It looks like Heat is being too keen in assuming that the harvested registry
keys can be mapped to COM registration. Removing the mscoree
element simply breaks the COM registration of that .NET component, and
adding a Server="mscoree.dll" entry to the element (which seems like
the right thing to do) results in LGHT0094.
cheers,
Karim
--
View this message in context:
http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13239208
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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'. Please remove one of the entries or rename a part of the primary key to avoid the collision. It means that the Registry rows the Class element generates has the same Root, Key, and Name values as one of the RegistryValue elements. Again, please file a bug -- at least some of the generated RegistryValue elements can be omitted because they duplicate the strongly-typed Class/ProgId elements. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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 'reg9D78D592D2980BC3F33101F91D853AE6' is duplicated in table 'Registry'. Please remove one of the entries or rename a part of the primary key to avoid the collision. It means that the Registry rows the Class element generates has the same Root, Key, and Name values as one of the RegistryValue elements. Again, please file a bug -- at least some of the generated RegistryValue elements can be omitted because they duplicate the strongly-typed Class/ProgId elements. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
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, or specifying that Server="ComTest.TestThing.dll" in the Class element. Easy enough. The problem I'm having difficulty getting past is that when I try to light this, I get a message like this: Microsoft (R) Windows Installer Xml Linker version 3.0.2315.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. C:\projects\sandbox\COMTest.wxs(19) : error LGHT0130 : The primary key 'reg9D78D592D2980BC3F33101F91D853AE6' is duplicated in table 'Registry'. Please remove one of the entries or rename a part of the primary key to avoid the collision. The error is returned on the line containing the Class element. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
