Re: [WiX-users] COM registration weirdness

> Is this code significantly different than what is in heat? > Can we improve heat as well? I didn't look at heat's sourcecode when I wrote my utility, but it uses the same registry redirection technique. I've looked at RegistryHarvester.cs and I can't see where it deals with the Class/TypeLib t

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Troy Howard" <[EMAIL PROTECTED]> writes: > This application is a beast, and the installer has to tame it. What a > project At least I have a nice view of downtown Portland at night from > the 11th floor of this building. When I removed self-reg component

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Troy Howard" <[EMAIL PROTECTED]> writes: > Should I just do a regasm /reg and then convert that to WiX code? That's what I've done in the past and it worked just fine. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download

Re: [WiX-users] COM registration weirdness

"First, you should not be packaging someone else's resources in your MSI. You should be getting a Merge Module that has all of the COM and DLL and most importantly the *correct* Component GUIDs. That's what Merge Modules were designed for." You might want to tell Microsoft that and get a merge m

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, Bob Arnson <[EMAIL PROTECTED]> writes: > Neil Sleightholm wrote: > > My untested theory is that when you call DllRegisterServer on a VB6 DLL > > it either calls DllRegisterServer on MSVBVM60.dll or the code from it is > > embedded into the VB6 dll. > > In my

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, Rob Mensching <[EMAIL PROTECTED]> writes: > MSXML3 [I think] used to have SelfReg and it a ccounted for a percentage > point or two of installation failures for Office... that was lot of > money wasted on SelfReg. Wow. That is an awesome data point! -- "The

Re: [WiX-users] COM registration weirdness

work. -Original Message- From: Troy Howard [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 23:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness Ok, I found a process that works... First, I had to explicitl

Re: [WiX-users] COM registration weirdness

It's both. The application is written in VB6. It uses COM DLLs written in various languages, including C++, VB6, and .NET. The installer needs to be able to register all of these things. The non-.Net COM DLLs seem to be doing alright with the SelfRegCost attribute applied, but now the .Net DLLs a

Re: [WiX-users] COM registration weirdness

I appreciate the feedback. In the short term, I've added the SelfRegCost attribute to the file tags for the non-.Net COM DLLs, and that seems to work fine. As for the DLLs themselves, I have no idea what langauge they were written in. We're using them within a legacy VB6 app, and wiring in new fun

Re: [WiX-users] COM registration weirdness

Is this code significantly different than what is in heat? Can we improve heat as well? -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2008 01:09 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration

Re: [WiX-users] COM registration weirdness

erience, advertising shortcuts and extensions works well but COM advertising has some a rather unpleasant user experience and side effects. -Original Message- From: Troy Howard [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2008 02:04 To: General discussion for Windows Installer

Re: [WiX-users] COM registration weirdness

scussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness > Regarding SelfReg, or not I'm not completely sure I drink > the Kool-Aid on this one. So, I understand that SelfRegCost > violates transactability rules (spell checker says > transact

Re: [WiX-users] COM registration weirdness

Heat. Neil -Original Message- From: Richard [mailto:[EMAIL PROTECTED] Sent: 01 October 2008 23:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness In article <[EMAIL PROTECTED]>, "Neil Sleightholm" &

Re: [WiX-users] COM registration weirdness

> Regarding SelfReg, or not I'm not completely sure I drink > the Kool-Aid on this one. So, I understand that SelfRegCost > violates transactability rules (spell checker says > transactability is not a word >shrug<) due to MSI and how it > handles that... But what then IS the recommended way t

Re: [WiX-users] COM registration weirdness

Regarding SelfReg, or not I'm not completely sure I drink the Kool-Aid on this one. So, I understand that SelfRegCost violates transactability rules (spell checker says transactability is not a word >shrug<) due to MSI and how it handles that... But what then IS the recommended way to deal wit

Re: [WiX-users] COM registration weirdness

Neil wrote: > I have tried a > few times to remove the unrelated code and never successfully > got the component to work or to leave the machine working on > uninstall. Have you ever generated the WiX registry code for > VB6 COM component? Has anyone? Neil, I have. I wrote a custom build task tha

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > Have you ever generated the WiX registry code for > VB6 COM component? Has anyone? Oh, I almost forgot -- yes, I have registered VB6 COM components manually by populating the Class, etc., tables. I haven't don

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > Richard > > >> The answer to that is pretty simple -- you ignore anything that's not > >> related to your component. > > I think you are missing the point (or I am), how do I know it is not > related? Well,

Re: [WiX-users] COM registration weirdness

nyone? Neil -Original Message- From: Richard [mailto:[EMAIL PROTECTED] Sent: 01 October 2008 21:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > The key issue here is what do you need to exclude when registering a VB6 > DLL or is it possible to monitor it so we find the key information. Can > you recommend a registry monitoring tool that works for VB6 DL

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, Rob Mensching <[EMAIL PROTECTED]> writes: > Note, those actions are only necessary if you are using the Advertised > features of COM registration otherwise it's all just Registry rows. True. So let me state it another way -- is there an ICE that fails if you

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Evans, Jim" <[EMAIL PROTECTED]> writes: > Interestingly, ProcMon (the successor to RegMon) was no help here, as > all of the registration calls were being sent to HKEY_CLASSES_ROOT, > which does not differentiate between which elements are going to the > user

Re: [WiX-users] COM registration weirdness

Neil Sleightholm wrote: > My untested theory is that when you call DllRegisterServer on a VB6 DLL > it either calls DllRegisterServer on MSVBVM60.dll or the code from it is > embedded into the VB6 dll. > In my experience, self-reg code gets extra-aggressive in response to bug reports to respon

Re: [WiX-users] COM registration weirdness

-Original Message- From: Richard [mailto:[EMAIL PROTECTED] Sent: 01 October 2008 16:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]

Re: [WiX-users] COM registration weirdness

Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness Ok, I found a process that works... First, I had to explicitly add: then for each .net com dll, i ran heat against it to generate a wxs. I th

Re: [WiX-users] COM registration weirdness

ertise-COM-information-in-MSI.aspx) and I don't *think* heat generates advertised by default. -Original Message- From: Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 08:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Troy Howard" <[EMAIL PROTECTED]> writes: > [...] The default sequence doesn't > include the com registration actions that read the class table/etc. IMO, that seems like a bug in WiX. IIRC, the recommended default install sequence *does* include all the regi

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > All regsvr32 does is call DllRegisterServer on the DLL, what happens in = > here is voodoo! It is perfectly legal to d anything you want in this = > call and is the reason why self registration is frowned upon.

Re: [WiX-users] COM registration weirdness

Wednesday, October 01, 2008 03:14 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness All regsvr32 does is call DllRegisterServer on the DLL, what happens in here is voodoo! It is perfectly legal to d anything you want in this call and is the

Re: [WiX-users] COM registration weirdness

for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > >> By the time it's a COM object, VB6 or C++ it doesn't make any > >> differenc

Re: [WiX-users] COM registration weirdness

Ok, I found a process that works... First, I had to explicitly add: then for each .net com dll, i ran heat against it to generate a wxs. I then fixedup those wxs files in the following manner: 1. Wrap the Class/ProgID

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Neil Sleightholm" <[EMAIL PROTECTED]> writes: > >> By the time it's a COM object, VB6 or C++ it doesn't make any > >> difference. > > That is a nice theory [...] Its not a theory. An OCX from VB6 is just a DLL with a well defined entry point for registerin

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Troy Howard" <[EMAIL PROTECTED]> writes: > So, in my efforts to resolve the .Net COM issues, [...] Earlier, this thread was talking about registering a VB6 control. Now you're talking about registering a .NET assembly for COM interop. So which is it? I've

Re: [WiX-users] COM registration weirdness

So, in my efforts to resolve the .Net COM issues, I've tried out this process: 1. Generate .reg files with regasm /regFile 2. Convert .reg files to .wxs using tallow (WiX2) 3. Fixup .wxs files using WixCop (WiX3). 4. Fixup those fixed-upped files removing the nested and duplicate registry entries.

Re: [WiX-users] COM registration weirdness

>> By the time it's a COM object, VB6 or C++ it doesn't make any >> difference. That is a nice theory and I believed it but just couldn't get my head around registering VB6 COM DLL's (C++ are fine) in the end I ended up using self registration (SelfRegCost=1). I'm sure there is some voodoo going o

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, Rob Mensching <[EMAIL PROTECTED]> writes: > If anyone does figure it out, it'd be good to understand what is going on. > I don't know VB (let alone VB6) and things work great for my C++/ATL based > COM objects. By the time its a COM object, VB6 or C++ it does

Re: [WiX-users] COM registration weirdness

o: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration weirdness Hi Jim, Did you ever figure this out? I'm in basically the same situation. I have a VB6 application that uss numerous third party COM DLLs, and some in-house .Net COM DLLs. I've included

Re: [WiX-users] COM registration weirdness

Hi Jim, Did you ever figure this out? I'm in basically the same situation. I have a VB6 application that uss numerous third party COM DLLs, and some in-house .Net COM DLLs. I've included all the appropriate bits of WiX code (AFAICT), but the registration doesn't seem to be effective. Running regs

Re: [WiX-users] COM registration weirdness

Richard wrote: > RegMon will reveal all. You can get it from the sysinternals portion > of Microsoft's web site. Not always. As I said from my original post, I monitored the installation using ProcMon (the successor to RegMon), and it looked like everything was okay. The problem turned out to be

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Tony Juricic" <[EMAIL PROTECTED]> writes: > I know this approach is not officially recommended but it is hard to see > what some third-party COM servers do with the Registry. RegMon will reveal all. You can get it from the sysinternals portion of Microsoft'

Re: [WiX-users] COM registration weirdness

In article <[EMAIL PROTECTED]>, "Evans, Jim" <[EMAIL PROTECTED]> writes: > I know this isn't the exact forum for this, but I'm really confused and > don't know where else to turn. I'm in the process of moving our > installer to an msi-based install using WiX. Our application is fairly > comp

Re: [WiX-users] COM registration weirdness

: Evans, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2008 6:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM registration weirdness I know this isn't the exact forum for this, but I'm really confused and don't know where else to turn. I'm in the p

[WiX-users] COM registration weirdness

I know this isn't the exact forum for this, but I'm really confused and don't know where else to turn. I'm in the process of moving our installer to an msi-based install using WiX. Our application is fairly complex, including .NET assemblies, a client-side application, Windows services that run on