Exposing an already running singlton .NET component as COM server

[Omer S]

Hello all, I'm in the process of moving the system I work on from C++/MFC/COM to the .NET world. As usual, a lot of legacy code must remain as is client-wise ... The dilemma I'm facing is the following: I'm using a sort of home-made IOC framework to instantiate and hold a singleton .NET component. For performance reasons (avoid context switching) I would like to expose it to a native C++ client which till today instantiated the 'good old' COM component (replaced by the .NET component) using CoCreate... I cannot touch the client's code, and it needs to interact with the .NET component already instantiated. Any ideas? Will registering with the ROT do the trick? Thanks, Omer