Recently used heat to harvast a directories worth of COM components. Most of
the components were authored like:
Component
..File
....Class
......ProgId
........ProgId
However 2 of the components were authored like:
Component
..File
....Class
......ProgId
......ProgId
The ProgId elements had unique Id's and Descriptions but failed to build with
an error message similar to:
The primary key 'regHASH.GUID' is duplicated in table 'Registry'. Please
remove one of the entries or rename a part of the primary key to avoid the
collosion.
I 'fixed' it ( haven't tested the COM components in an integration lab yet ) by
nesting the ProgIds. I looked at the registry table and it looks correct at
first glance.
I'm trying to understand if this is a bug in the COM component, in authoring
the XML or in building the XML. Has anyone ever seen this before?
Thanks,
Chris
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
