Re: [WiX-users] COM+ registration help

Neil Sleightholm wrote > I'll see if I can make a simple repro first and try and come up with some > ideas. > > > dmm - can you raise a defect so this is not lost? Thanks Neil! I believe there are already a couple of bug reports / fix requests for this but I will double-check and enter one if m

Re: [WiX-users] COM+ registration help

all, Setup is just XCOPY, right?? :-)" Regards, Chris From: "Katherine Moss" Sent: Friday, March 22, 2013 9:53 AM To: "chr...@iswix.com" , "General discussion for Windows Installer XML toolset." Subject: RE: [WiX-us

Re: [WiX-users] COM+ registration help

or Windows Installer XML toolset.; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM+ registration help My COM+ experience is 10 years old but here's something I'm wondering: I wonder if what ever classes that are in System.Enterprise.Services ( or whatever th

Re: [WiX-users] COM+ registration help

. I don't care enough about COM+ to find out so just take that public thought as-is. From: "Neil Sleightholm" Sent: Friday, March 22, 2013 2:46 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-user

Re: [WiX-users] COM+ registration help

see what version of .NET is loaded in the same process >>space as >> you msi? >> >> -Original Message- >> From: DexterSinister [mailto:dma...@nt4hire.com] >> Sent: 20 March 2013 21:23 >> To: wix-users@lists.sourceforge.net >> Subject: Re: [WiX

Re: [WiX-users] COM+ registration help

tarting your msi and then using something like process > explorer to see what version of .NET is loaded in the same process space as > you msi? > > -Original Message- > From: DexterSinister [mailto:dma...@nt4hire.com] > Sent: 20 March 2013 21:23 > To: wix-users@

Re: [WiX-users] COM+ registration help

Christopher Painter-2 wrote > http://blog.torresdal.net/2008/10/24/wix-and-dtf-using-a-custom-action-to-list-available-web-sites-on-iis/ Thanks! I'll check this out ... -dmm -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/COM-registration-help-

Re: [WiX-users] COM+ registration help

http://blog.torresdal.net/2008/10/24/wix-and-dtf-using-a-custom-action-to-li st-available-web-sites-on-iis/ From: "DexterSinister" Sent: Thursday, March 21, 2013 11:29 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM+ registr

Re: [WiX-users] COM+ registration help

Christopher Painter-2 wrote > If that's the case, a DTF custom action wouldn't have that problem. Thanks for the tip ... I've never done anything with DTF, do you have any suggestions on how to get started ? Thanks again for your time and attention, -dmm -- View this message in context: h

Re: [WiX-users] COM+ registration help

If that's the case, a DTF custom action wouldn't have that problem. From: "Neil Sleightholm" Sent: Wednesday, March 20, 2013 4:49 PM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users]

Re: [WiX-users] COM+ registration help

users@lists.sourceforge.net Subject: Re: [WiX-users] COM+ registration help Yes, Neil ... RegSvcs works fine for either version of the DLL, installs fine ... uninstalls fine ... Weird, eh? I'm going to take a look at the ComPlus extension code to see if I can find any obvious reason why it's not

Re: [WiX-users] COM+ registration help

Yes, Neil ... RegSvcs works fine for either version of the DLL, installs fine ... uninstalls fine ... Weird, eh? I'm going to take a look at the ComPlus extension code to see if I can find any obvious reason why it's not working ... not familiar territory, but I may as well give it a shot ... Th

Re: [WiX-users] COM+ registration help

leightholm; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] COM+ registration help Neil, I'm just giving my opinion. ArrayList and HashTable is still in the .NET Framework but that doesn't mean you should use it instead of List and Dictionary. COM+ is a

Re: [WiX-users] COM+ registration help

uot; , "General discussion for Windows Installer XML toolset." Subject: RE: [WiX-users] COM+ registration help I am not sure I follow what has remoting API got to do with installing COM+ services? System.EnterpriseServices is still part of all versions of .NET and is used to support C

Re: [WiX-users] COM+ registration help

+ installation issues. Neil From: Christopher Painter [mailto:chr...@iswix.com] Sent: 20 March 2013 15:59 To: Neil Sleightholm; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM+ registration help I had a really good response typed up but then IE10 crapped out on me like it

Re: [WiX-users] COM+ registration help

e remoting API's about 4 times since then. Regards, Chris From: "Neil Sleightholm" Sent: Wednesday, March 20, 2013 10:47 AM To: "chr...@iswix.com" , "General discussion for Windows Installer XML toolset." Subject: Re:

Re: [WiX-users] COM+ registration help

2013 3:56 AM >To: "General discussion for Windows Installer XML toolset." > >Subject: Re: [WiX-users] COM+ registration help > >I think Rob is right, the WiX code uses an assembly >System.EnterpriseServices (method RegistrationHelper) to install COM+ this >doesn

Re: [WiX-users] COM+ registration help

wcf et al... From: "Neil Sleightholm" Sent: Wednesday, March 20, 2013 3:56 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] COM+ registration help I think Rob is right, the WiX code uses an assembly Sys

Re: [WiX-users] COM+ registration help

> > >On Tue, Mar 19, 2013 at 2:26 PM, Neil Sleightholm >wrote: > >> Does the .NET 4.0 component install to COM+ ok if you do it manually? >> >> -Original Message- >> From: DexterSinister [mailto:dma...@nt4hire.com] >> Sent: 19 March 2013 20:34 &g

Re: [WiX-users] COM+ registration help

. On Tue, Mar 19, 2013 at 2:26 PM, Neil Sleightholm wrote: > Does the .NET 4.0 component install to COM+ ok if you do it manually? > > -Original Message- > From: DexterSinister [mailto:dma...@nt4hire.com] > Sent: 19 March 2013 20:34 > To: wix-users@lists.sourceforge.net &g

Re: [WiX-users] COM+ registration help

Does the .NET 4.0 component install to COM+ ok if you do it manually? -Original Message- From: DexterSinister [mailto:dma...@nt4hire.com] Sent: 19 March 2013 20:34 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM+ registration help Hi Rob - Your 'nothing' i

Re: [WiX-users] COM+ registration help

Hi Rob - Your 'nothing' is probably more than my nothing on this topic, so thanks in advance for any assistance and insight you can provide. Here's the relevant log segment: ** ComPlusInstallExecuteCommit: Entering ComPlusInstallExecuteCommit in C:\WINDOWS\Installer\MSI29.tmp, version 3

Re: [WiX-users] COM+ registration help

I know basically nothing about COM+ but a little detail about the exact error codes you are hitting might help others. On Mon, Mar 18, 2013 at 10:05 AM, DexterSinister wrote: > Like the subject line says ... > > I'm using WiX v3.7.1224.0 to build an installation package for an app that > has a

[WiX-users] COM+ registration help

Like the subject line says ... I'm using WiX v3.7.1224.0 to build an installation package for an app that has a COM+ service application ... I've tried to use the COM+ custom actions and have had nothing but failures, this installer & app were working until the app was updated to use .NET v4 - I

Re: [WiX-users] com registration

Anil Patel [mailto:apatel...@googlemail.com] Sent: Wednesday, July 27, 2011 4:39 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] com registration Hi Daniel, 1) For a COM dll, heat should generate the appropriate registry data. 2) For a COM EXE server, heat will not generate

Re: [WiX-users] com registration

Hi Daniel, 1) For a COM dll, heat should generate the appropriate registry data. 2) For a COM EXE server, heat will not generate the the registry data but you can do the following.: a) Use RegSpy2 to extract the registry data into a reg file. So if my COM exe is called TestCOM.exe, you would i

[WiX-users] com registration

I'm using heat to generate the fragment for my COM object. After installing the MSI, the CLSID entries are not created in the registry. Should I add Registry elements to my WXS file manually or am I doing something wrong? Thanks, Dariel -

Re: [WiX-users] COM Registration

Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: swapna.rachako...@thomsonreuters.com [mailto:swapna.rachako...@thomsonreuters.com] Sent: 01 April 2011 15:07 To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM

[WiX-users] COM Registration

Hello experts Could anyone explain me How to register COM using WiX ? Thanks in advance Swapna -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself;

[WiX-users] COM registration with heat or ComPlusExtension?

We have a mix of native and .NET components, and use COM for interop. Until now, I have used heat.exe to generate wix fragments for installing .NET assemblies and registering them as COM servers (like regasm.exe would do). However, somebody just told me that you can also use the ComPlusExtension t

Re: [WiX-users] COM registration of a DLL

ssion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration of a DLL I am not fully sure what you are asking but what I was referring to is binder variables, see here: http://wix.sourceforge.net/manual-wix3/light.htm <http://wix.sourceforge.net/manual-wix3/light.htm&g

Re: [WiX-users] COM registration of a DLL

stems.com> From: David Thielen [mailto:da...@windward.net] Sent: Mon 12/07/2010 22:36 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] COM registration of a DLL How do I get the reference to automatically set the version num

Re: [WiX-users] COM registration of a DLL

s.com] Sent: Monday, July 12, 2010 1:09 AM To: General discussion for Windows Installer XML toolset.; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration of a DLL Could you explain what you mean by updating the files version? Is this a .NET COM assembly? If so you can use the bi

Re: [WiX-users] COM registration of a DLL

...@x2systems.com <mailto:n...@x2systems.com> From: David Thielen [mailto:da...@windward.net] Sent: Sat 10/07/2010 00:35 To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM registration of a DLL Hi; What's the easiest way to have WIX

Re: [WiX-users] COM registration of a DLL

On 7/9/2010 7:35 PM, David Thielen wrote: > What's the easiest way to have WIX perform COM registration of a DLL? > Preferably a way where we don't have to update the file's version numbers. > Use Heat then replace the hard-coded version number with a preprocessor variable. -- sig://boB ht

Re: [WiX-users] COM registration of a DLL

On Fri, 9 Jul 2010 21:44:51 -0600 David Thielen wrote: > That sets the version number so we then have to update for every > build. I'd prefer to avoid that. Isn't there an attribute to the file > command that tells the system to register it? There is, but you should read http://stackoverflow.com

Re: [WiX-users] COM registration of a DLL

09, 2010 6:19 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] COM registration of a DLL Use the heat tool? -Original Message- From: David Thielen [mailto:da...@windward.net] Sent: Friday, July 09, 2010 4:35 PM To: wix-users@lists.sourcefor

Re: [WiX-users] COM registration of a DLL

Use the heat tool? -Original Message- From: David Thielen [mailto:da...@windward.net] Sent: Friday, July 09, 2010 4:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM registration of a DLL Hi; What's the easiest way to have WIX perform COM registration of

[WiX-users] COM registration of a DLL

Hi; What's the easiest way to have WIX perform COM registration of a DLL? Preferably a way where we don't have to update the file's version numbers. ??? - thanks - dave -- This SF.net email is sponsored by Sprint What w

Re: [WiX-users] COM+ registration for a 64 bit assembly.

discussion for Windows Installer XML toolset.' Subject: [WiX-users] COM+ registration for a 64 bit assembly. I was trying to use Heat.exe to generate the registry entries but this fails because heat is 32 bit and the assembly I'm trying to get the registry information for is 64 bit.

[WiX-users] COM+ registration for a 64 bit assembly.

I was trying to use Heat.exe to generate the registry entries but this fails because heat is 32 bit and the assembly I'm trying to get the registry information for is 64 bit. What are we supposed to use to get the right registration entries for this? Also, I see references to a Complus extensio

Re: [WiX-users] COM Registration - schema problem?

Hi Bob, I found MS KB article describing how to alias COM component manually, which creates exactly same registry entries as the WIX code should. I filed defect report: https://sourceforge.net/tracker2/?func=detail&aid=2644742&group_id=105970&atid=642714 KB article: http://support.microsoft.com/

Re: [WiX-users] COM Registration - schema problem?

Maciej Oszutowski wrote: > Seems that ProgId supports *only one* child ProgId element. > Yes. It's not clear that version-independent ProgIds are valid as a general "alias" function. If you can find some doc that says it should, please file a bug report with the link. -- sig://boB http://jo

Re: [WiX-users] COM Registration - schema problem?

Hi Bob, Candle output: Project.wxs(474): error CNDL0107: Schema validation failed with the following error at line 1, column 67675: The element 'ProgId' in namespace 'http://schemas.microsoft.com/wix/2006/wi' has invalid child element 'ProgId' in namespace 'http://schemas.microsoft.com/wix/

Re: [WiX-users] COM Registration - schema problem?

Maciej Oszutowski wrote: > Few days ago I found a component which has been correctly decompiled > from msm, but source generated by dark can't be compiled due to schema > validation. > What's the actual error? ProgId supports child ProgId elements. -- sig://boB http://joyofsetup.com/ -

[WiX-users] COM Registration - schema problem?

Hi, I'm in the long way of converting tons of InstallShield projects to WIX last days. Usually I use dark on compiled merge modules and do some cleanup manually. In most cases this is enough. Few days ago I found a component which has been correctly decompiled from msm, but source generated by dar

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

Re: [WiX-users] COM+ Registration in WiX3

There is a COM+ custom action and compiler extension. Check out wix.chm for details. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Faden Sent: Wednesday, July 16, 2008 1:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM

[WiX-users] COM+ Registration in WiX3

Hi, I want to generate a COM+ component based on my dll ( C++/ATL). Does anybody has a hint where I can find some documentation about that topic? Thx in advance Mike -- Dr.Michael Fadenfon: +49(0)228-98549-51 kippdata GmbH fax: +49(0)228-98549-50 Bornheimer Str. 33a Ema

Re: [WiX-users] COM registration

Thomas Svare wrote: Everything is technically working properly but I've been asked to provide a work-around for a UI issue. The problem I'm dealing with is the default registry entry for InprocServer32 is being written using the short file and path name. Is there a way to force the default

[WiX-users] COM registration

Hello, I'm using Wix 2.0.5805 and the following code: Everything is technically working properly but I've been asked to provide a work-around for a UI issue. The problem I'm dealing with is the defau

Re: [WiX-users] COM registration problems

esday, December 12, 2007 3:05 AM To: 'Szentpali Janos'; [EMAIL PROTECTED]; wix-users@lists.sourceforge.net; Wilson, Phil Subject: RE: [WiX-users] COM registration problems Thanks for your attention! The problem was that the typelib´s of some comvisible assemblies were not registered. I

Re: [WiX-users] COM registration problems

That happened to me too, but I shut up because I thought there must be a better way and I was about to be educated. :) Tobias Holm wrote: > Thanks for your attention! > > The problem was that the typelib´s of some comvisible assemblies were not > registered. I thought that tallow would extract th

Re: [WiX-users] COM registration problems

Thanks for your attention! The problem was that the typelib´s of some comvisible assemblies were not registered. I thought that tallow would extract this information as well when I ran tallow -c on the dlls. I solved it by: 1 running regasm on my comvisible assemblies. 2 manually extracting the t

Re: [WiX-users] COM registration problems

om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tobias Holm Sent: Tuesday, December 11, 2007 9:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM registration problems Hi all, Im having serious problems with a registration of a com-dll. When I install it manually wit

Re: [WiX-users] COM registration problems

I don't think the ("TYPE_E_CANTLOADLIBRARY ($80029C4A)") error comes from the way it is installed. It is more likely a dependency problem: another COM component that your library is using (maybe a type library that it implements) might be missing (or is in the path in the context of the user that r

[WiX-users] COM registration problems

Hi all, Im having serious problems with a registration of a com-dll. When I install it manually with regsvr32, everything works fine. To install it with wix I do the following: 1. Create a wix file with a component-element containing a file-element pointing to my my dll. 2.

Re: [WiX-users] COM Registration of .Net assembly in v2

Meese Sent: 30 March 2007 16:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] COM Registration of .Net assembly in v2 Hello, We tried v3, but ran into trouble with some 3rd party merge modules that are needed for our application. What I am running up against now is that the ac

  1   2   >