PROTECTED]
Sent: Wednesday, August 30, 2006 11:41 AM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] using heat to harvest COM objects that do not
have the '.dll' extension.
Yesin this case, it's used
as the unmanaged > managed code in
ilto:[EMAIL PROTECTED]]
Sent: Wednesday, August 30, 2006 6:59 AM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] using heat to harvest COM objects that do not
have the '.dll' extension.
As of last week's release, .tlb
files didn't work eithe
:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 6:59 AM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] using heat to harvest COM objects that do not
have the '.dll' extension.
As of last week's release, .tlb
files didn't work either.
should be in the next WiX
3.0 release.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Ali-Akber
Saifee
Sent: Wednesday, August 30, 2006 2:00 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] using heat to harvest COM objects that do not have
the '.d
harvest COM objects that do not have
the '.dll' extension.
Some of my installation components use DirectShow filters...
(*.ax files).. when i try to harvest them with heat the class information +
registry information is not extracted. I suspect this is due to a wildcard
filter wh
Some of my installation components use DirectShow filters... (*.ax files).. when i try to harvest them with heat the class information + registry information is not extracted. I suspect this is due to a wildcard filter which is not classifying .ax files as possible candidates for COM objects...
i t
6 matches
Mail list logo
