In case anyone is interested, I was being stupid (as I thought!) :-)
All I had to do was wrap the Registry Keys inside a Component element, then
wrap that inside a DirectoryRef element (to "TARGETDIR")
Then I referenced that in my Feature and hey ho, all works perfectly!
(Well, except for the f
27;General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Heat and COM executable registry extraction
Phil,
Thanks for your tip. Here is what I did to solve the problem:
1) As Phil suggested I ran RegSpy2 and gathered all the registry
information from the COM Executable a
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil
Sent: 2008-Oct-09 Thu 12:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and COM executable registry extraction
If you scroll down here:
http://installsite.org/pages
Kamil Mierzejewski wrote:
>
> The tool is not publicly available. All I can do is to post source code
> (C++) or the compiled binary on your e-mail address.
>
> You can learn how to use it from the source - it's very small and simple.
>
> I think it is a piece of functionality that could be i
CTED]
Sent: Thursday, October 09, 2008 4:32 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Heat and COM executable registry extraction
Kamil & Michael, thanks a lot for the information you have provided.
Kamil, I am very interested in trying
Installer XML toolset.
Subject: Re: [WiX-users] Heat and COM executable registry extraction
The tool is not publicly available. All I can do is to post source code
(C++) or the compiled binary on your e-mail address.
You can learn how to use it from the source - it's very small and simpl
09 Thu 6:01 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Heat and COM executable registry extraction
>
> Hi,
>
> I also encountered this problem. My solution was to design a special
> tool which scans .tlb files and generates WiX co
inal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kamil
Mierzejewski
Sent: 2008-Oct-09 Thu 6:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and COM executable registry extraction
Hi,
I also encountered this problem. My solu
Hi,
I also encountered this problem. My solution was to design a special
tool which scans .tlb files and generates WiX code from them.
details in my comment here:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1468663&group_id=105970
The tools assumes that classes defined in the t
Hi Arun,
I've been experiencing the same kind of problems and I posted a question about
it recently. See
the
http://n2.nabble.com/Heat-problem-harvesting-class-from-type-library-td1303554.html
I believe the problem is that for executables (.exe out-of-process COM Servers)
the WiX heat tool
can
Hi guys,
I need to install a couple of COM executables and I have been trying to use
Heat (ver 3.0.4513) to extract the COM information. From what I see heat
extracts part of registry information into the fragment but the information
seems to be less than what is needed. After installation, inv
11 matches
Mail list logo
