One way is to create a COM shim over .NET remoting that accomplishes
such functionality. That way you only really need to COM-enable the
C# client library that exposes the methods you want to be callable,
and then that library forwards them to the out-of-process .NET server
via Remoting (or other .NET communication technology of your choice).
On Feb 11, 10:28=A0am, NN Ott <nonot...@gmail.com> wrote:
> Hello,
>
> I don't know much about COM or C++, so perhaps these are silly
> questions:
>
> 1) Without resorting C++/ATL wrapper program, can I make an out-of-
> process C#/.net 4.0 application that's callable via COM from
> traditional COM clients? =A0 (I don't need to call in to COM. Only to be
> called.)
>
> 2) Is there anything new in .NET 4.0 that would make this easier vs.
> 3.5?
>
> 3) The tutorials I can find all seem to assume a strong working
> knowledge of C++/ATL. =A0Does anyone know of a resource that only
> assumes C# knowledge?
>
> Thank you