I'll try both. (I have tried to get an assignment agreement before but
never received a reply.)
Thanks
Neil
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 25 February 2007 18:21
To: Neil Sleightholm
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX3 Error: The primary
So I guess the next question would be how do I go about getting this
changed?
Neil
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 21 February 2007 05:13
To: Neil Sleightholm
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated
in
Neil Sleightholm wrote:
So I guess the next question would be how do I go about getting this
changed?
Two ways:
1. Submit a patch and submit an assignment agreement.
2. File a feature request.
--
sig://boB
http://bobs.org
Neil Sleightholm wrote:
I think the full solution would be to modify the Class element to
fully support .Net COM components, for these it would also be
necessary to allow the addition of the keys Assembly, RuntimeVersion
and CodeBase. It may be possible to automatically create these from
I think I understand this a bit more now and it would appear to be
limitation of the Class element.
To register .Net COM components you need to set the InprocServer32 to
mscoree.dll and I can't see how you can do this with the Class
element as this is not a file that is installed by your
Neil,
I had the same issue when using tallow on a .reg file for an ActiveX.exe.
It turned out that tallow was creating nested registry keys, and those don’t
compile.
For example (and this is from memory, so I’m sure it’s not syntactically
correct):
registry root=”HLCR”
Thanks that gave me the clue I was missing. I think the problem is that
the code fragment is followed by:
RegistryKey Root=HKCR
Key=CLSID\{1F235F80-8889-4C2D-96E5-B4C3D4C186C9}\InprocServer32
Action=createAndRemoveOnUninstall
RegistryValue Value=mscoree.dll Type=string Action=write /
This bug in heat has been reported a couple times. Unfortunately, people just
keep working around the bug instead of helping make a fix for it. So, it
hasn't been fixed because no one is currently maintaining heat.exe.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil
I'll see if I can contribute by working out what the problem is.
Neil
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 30 January 2007 17:41
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] WiX3 Error: The primary key xxx is
duplicated in table
Is this a bug in tallow/heat (I’m using tallow) or is it an issue with the
compiler? The xml makes sense, and I’m just using a xls to transform
de-normalize it. It seems like the compiler is at fault for not creating
the registry table entries correctly from seemingly valid xml.
John
John Cole wrote:
Is this a bug in tallow/heat (I’m using tallow) or is it an issue with
the compiler? The xml makes sense, and I’m just using a xls to
transform de-normalize it. It seems like the compiler is at fault for
not creating the registry table entries correctly from seemingly
I wonder if anyone could give me some pointers on what the following
error means:
The primary key 'regCEE002B6E272C08B0F4B8191A9027490' is duplicated in
table 'Registry'. Please remove one of the entries or rename a part of
the primary key to avoid the collision.
I think this is generated by
12 matches
Mail list logo
