Access COM objects on another box from .NET (without deprecated DCOM, remoting)

Question

I have to integrate my .NET server app with a vendor's product. The vendor's product will be on its own server and has a supported & documented API, but alas, only as COM objects. Since DCOM and .NET remoting are both deprecated, is there a supported (i.e. not at risk of being removed in .NET 5) way to perform this integration without having to create & install a web service on the vendor box & web client on my box to proxy these requests across the network to COM?

Note that I'm very comfortable writing & consuming web services (REST when I can, SOAP when I have to). I'd just like to keep the topography of this app simple, avoid dual deploys, etc. For the same reason, I've avoided WCF since it seems like a lot of overhead, but if WCF supports exposing the underlying COM interface over the network, I'd happily use it. Otherwise, I guess I'm designing, writing, deploying, & consuming this new web service. Please show me I don't have to do this!

Answer 1

You might consider using WCF features for integration with COM+ applications