Re: [WiX-users] using heat to harvest COM objects that do not have the '.dll' extension.

Hehe, alright, I just fixed it. This 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

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 eitheralthough I didn't verify that it was already registered prior to harvesting, as I believe that's a pre-req?On 8/30/06, Derek Cicerone [EMAIL PROTECTED] wrote: Hehe, alright, I just fixed it. This should be in the next WiX

Re: [WiX-users] using heat to harvest COM objects that do not have the '.dll' extension.

.tlb files arent supported yet. I thought those were usually compiled into a .dll or other file when shipped to the customer. Do you ship the .tlb as part of your setup? Does the .tlb register a separate .dll file in the actual registry keys? Derek From: Brad Davis [mailto:[EMAIL

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 interface for a .NET COM-callable wrapper assembly. I'm not an expert, but the process we used to get around the issue today yeilded registration nodes for the .tlb and the associated assemblygoing around Charlie's barn: 1. Add a

Re: [WiX-users] using heat to harvest COM objects that do not have the '.dll' extension.

I see. Thank you for explaining that Ill add .tlb to the list of known self-reggable file extensions. Hopefully this should be in the next build. Please let me know if it works for you (without having to use VSI preferably J). Thanks, Derek From: Brad Davis [mailto:[EMAIL