My previous question was maybe not so good formulated.
I will explain my query as follow:

Do you know how to simulate in C#, a VB6 Activex EXE Standalone application which exposes a com visible object (IDispatch wrapper class) already instanced in the 'activex exe like' c# application? The clients accessing it via creatobject / getobject will always get a reference on this object.

This does not seem to be so straight forward as I experimented in vb.net.
Is it related to .net interop ?

If I understand the best way will be to expose a .NET Remoting object (application life time) then creating a COM interop class library which will be used like a tunnel between the two communication solutions.

If I understand the best way will be to expose a .NET Remoting object (application life time) then creating a COM interop class library which will be used like a bridge/connection between the two communications solution.

If I understand the best way will be to expose a .NET Remoting object (application life time) then creating a COM interop class library which will be used like a tunnel between the two communication solutions.

Abhinav, where did you see "static object" in the question? Please understand, "static object" is not a misnomer, but "object of static class" would be. These too things are not the same; and a static object is a usual thing. But who mentioned this object of static class?
--SA

OK, I looked at the first version of the OP's question and found a mention of "static object" there. No, there is nothing fundamentally wrong with this idea. Of course, practically, exposing of a static object by a class library is quite a bad design, but not a misnomer or something. (So, I did not vote this time.)
--SA

If I understand the best way will be to expose a .NET Remoting object (application life time) then creating a COM interop class library which will be used like a tunnel between the two communication solutions.