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
e new component fragment where it is necessary and
linked with the feature.
Thanks a lot for all your help.
-Arun
-Original 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 too
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
12, 2007 1:28 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and COM Registry Permissions
Hmm, all seems to be well if I set ALLUSERS=1 . Apparently the
default of an MSI is a per-user installation. So this isn't an issue
with heat or registry permissions at all, but u
Hmm, all seems to be well if I set ALLUSERS=1 . Apparently the
default of an MSI is a per-user installation. So this isn't an issue with
heat or registry permissions at all, but user error. Is this typical in
most installations where you have to explicitly set ALLUSERS=1?
On 2/12/07, Levi Wils
Sunday, July 09, 2006 12:30 PM
> To: [EMAIL PROTECTED]
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Heat and COM
>
> I believe they are the same as self-reg dlls. Both are registered using
> regsvr32
>
> Tallow knew how to handle these files, so we could alway
m: Shmarya Rubenstein [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 09, 2006 12:30 PM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and COM
I believe they are the same as self-reg dlls. Both are registered using
regsvr32
Tallow knew how to handle these fi
I believe they are the same as self-reg dlls. Both are registered using
regsvr32
Tallow knew how to handle these files, so we could always check it's code...
Derek Cicerone wrote:
>
> I’m not familiar with .ocx files – are they just like self-reg dll
> files? If so, I can make a small modificat
I’m not familiar with .ocx files – are they
just like self-reg dll files? If so, I can make a small modification to get
that working pretty quickly. If they are some other format of file, then we’d
have to write a special plugin to handle it – which would be a much longer
task.
Derek
16 matches
Mail list logo
