WCF service impersonating a COM component

Hi all. I am working on a project where I need to add a new component
to a system of COM/DCOM server components. Actually, I need to
replace one of the components. I was hoping I could replace it with a
WCF component. The key is that the other components' source code
cannot be changed. So these components would be calling
CoCreateInstance and the like, using the relevant CLSID and IID of the
COM component. Is it possible to implement things such that this will
transparently create/access a WCF service, and have this service
behave just like a COM component, so the other components are none the
wiser?

I looked around on the web and in some books but didn't see any
obvious way to do this. I'm hoping I just missed something. Does
anyone know if what I want to do is possible?

Thanks!

Carl

In theory, You should be able to do this.

You would have to create a CCW (Com Callable Wrapper for .NET) and then use
this wrapper to call into the WCF Service.

You can control the CLSID's and IID's using the COM Attribute settings of
the CCW.

HTH
-Dwightg@quicklearn.com

"carl_bevil@yahoo.com" wrote:

> Hi all. I am working on a project where I need to add a new component
> to a system of COM/DCOM server components. Actually, I need to
> replace one of the components. I was hoping I could replace it with a
> WCF component. The key is that the other components' source code
> cannot be changed. So these components would be calling
> CoCreateInstance and the like, using the relevant CLSID and IID of the
> COM component. Is it possible to implement things such that this will
> transparently create/access a WCF service, and have this service
> behave just like a COM component, so the other components are none the
> wiser?
>
> I looked around on the web and in some books but didn't see any
> obvious way to do this. I'm hoping I just missed something. Does
> anyone know if what I want to do is possible?
>
> Thanks!
>
> Carl
>
>

I'll look into that, thanks!

Carl