Re: [WiX-users] Solution for VB6 DLL

2009-02-10 Thread Rob Mensching
You know VB far better than I. What do you suggest? -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, February 09, 2009 23:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Solution for VB6 DLL I can't think of a way

Re: [WiX-users] Solution for VB6 DLL

2009-02-10 Thread Neil Sleightholm
them back. Neil -Original Message- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: 10 February 2009 17:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Solution for VB6 DLL You know VB far better than I. What do you suggest

[WiX-users] Solution for VB6 DLL

2009-02-09 Thread Andrew Ziem
My new MSI was working great in WiX 3.0.4805.0 (and Warsetup 3.12.0.0) except I needed to register a DLL which looks like it was made in VB 6 (it references MSVBVM60.DLL) I ran: heat.exe file foo.dll -out c:\foo.dll.wxs Then, I added the GUID, but I got errors: c:\wix3\candle.exe

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Rob Mensching
under v3.0 and heat.exe. I think we're close to getting it right. -Original Message- From: Andrew Ziem [mailto:ahz...@gmail.com] Sent: Monday, February 09, 2009 10:14 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Solution for VB6 DLL My new MSI was working great in WiX

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Andrew Ziem
On Mon, Feb 9, 2009 at 11:20 AM, Rob Mensching rob.mensch...@microsoft.com wrote: 1. Yes, using SelfRegCost is how you do SelfReg (regsvr32). It is considered bad. 2. Sounds like there is still a bug in the harvesting of VB6 DLLs still. Can you put all of this information plus the

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Neil Sleightholm
@lists.sourceforge.net Subject: [WiX-users] Solution for VB6 DLL My new MSI was working great in WiX 3.0.4805.0 (and Warsetup 3.12.0.0) except I needed to register a DLL which looks like it was made in VB 6 (it references MSVBVM60.DLL) I ran: heat.exe file foo.dll -out c:\foo.dll.wxs Then, I added the GUID

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Neil Sleightholm
I just tried the code you attached to the bug and it works for me with the -svb6 option. Neil -Original Message- From: Neil Sleightholm Sent: 09 February 2009 22:11 To: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Solution for VB6 DLL Can you try the -svb6 option on heat

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Rob Mensching
: Re: [WiX-users] Solution for VB6 DLL I just tried the code you attached to the bug and it works for me with the -svb6 option. Neil -Original Message- From: Neil Sleightholm Sent: 09 February 2009 22:11 To: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Solution for VB6 DLL Can

Re: [WiX-users] Solution for VB6 DLL

2009-02-09 Thread Neil Sleightholm
: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: 09 February 2009 23:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Solution for VB6 DLL Is there a way to autodetect those issues so -svb6 isn't necessary... or are there side effects to that option