Access to COM objects in another window from .NET (no obsolete DCOM removed)

I need to integrate my .NET server application with a vendor product. The vendor's product will be on its own server and has a supported and documented API, but, alas, only as COM objects. Since the remote DCOM and .NET are deleted, but is there a supported (i.e., not at risk of being removed in .NET 5) way to perform this integration without the need to create and install a web service in the window of the provider and web client on mine for proxying these requests all over the network on COM?

Please note: I am very comfortable writing and using web services (REST when I can, SOAP when I need). I would just like the topography of this application to be simple, avoid double deployment, etc. For the same reason, I avoided WCF, as this seems like a lot of overhead, but if WCF supports demonstrating a basic COM interface over a network, I would love to use it. Otherwise, I think I am developing, writing, deploying and using this new web service. Please show me that I do not need to do this!

+5
source share
2 answers

COM +, .

DCOM , COM + , . COM- , ( new, , ), .

+1

All Articles