Registration Free COM/.Net interop

re: Registration Free COM/.Net interop

Kevin Dente — Wed, 17 May 2006 19:08:07 GMT

Junfeng,
Thanks for the great info. One question - can you explain why only in-proc COM servers are supported for registration-free COM interop? Any plans to support out-of-proc servers in the future?

Kevin

re: Registration Free COM/.Net interop

junfeng — Wed, 17 May 2006 19:54:35 GMT

Neither Sxs or CLR COM interop supports out-of-proc servers. For Sxs, the question is how to pass the right activation context to the remote servers. I don't know about CLR, but I imagine it will have to write a bunch of complicated code to deal with RPC services. I don't see this change any time soon.

re: Registration Free COM/.Net interop

William Govan — Wed, 17 May 2006 22:05:31 GMT

Net Framework required for ATI

re: Registration Free COM/.Net interop

William Govan — Wed, 17 May 2006 22:07:37 GMT

net framework required for ATI.

Thank you
srlbowls@sympatico.ca

re: Registration Free COM/.Net interop

May Yip — Fri, 19 May 2006 02:07:00 GMT

Your article is very helpful, thank you. Could you point me in the right direction for getting COM interop in ASP.NET to work?

re: Registration Free COM/.Net interop

Chan Kok Kiet — Sun, 21 May 2006 07:13:42 GMT

Hi,
Does it apply COM with non-.NET (VC++, VB6, VFP) client application?

Thank you

re: Registration Free COM/.Net interop

Christian Weyer — Tue, 23 May 2006 18:18:59 GMT

Invaluable information, thanks a lot.

Now here I have an interesting one:

We have a plugin for Eclipse (you know, *the* Java IDE ;)) that uses a Java-to-COM lib to call my managed COM shell which in turn talks to my .NET assemblies.
For now I provide a script to register the COM component, but obviously aim at being completely registrion-free.

Any ideas?

Thanks.

re: Registration Free COM/.Net interop

Bob Riemersma — Sun, 04 Jun 2006 20:23:52 GMT

Stumbled over your blog after fiddling with Reg-Free COM in the context of XCopy-deploying VB6 EXEs. Seems to work great so far within the proscribed limitations. I even a wrote a small program to process a VB 6 project file and generate the manifests and create an XCopy folder, ready to burn on a CD or deploy to a flash drive. I suppose the next step is to have it descend through the dependencies of the libraries directly used by the VB project.

re: Registration Free COM/.Net interop

junfeng — Tue, 27 Jun 2006 11:41:14 GMT

Sorry Christian, I was on vacation.

You can read the "isolated application and side by side assembly" section in MSDN to understand how to make an application registration free. .Net framework assemblies simply use different syntaxes described in this article.

re: Registration Free COM/.Net interop

MIchael How — Mon, 31 Jul 2006 15:23:25 GMT

Any idea if the application does a CreateProcess, will inherit the COM mappings set up by the parent process? Or will that program need to be configure also?

re: Registration Free COM/.Net interop

junfeng — Tue, 01 Aug 2006 02:25:32 GMT

No the new process won't inherit the COM mapping of the parent process.