windows - Publishing COM/ActiveX interface using SOAP - what's the best solution? -


We have a COM API (Windows DLL file) that wants to use other system SOAP. What would be the best option for SOAP - should it be enabled?

The interesting parameters are:

  • License cost
  • Ease of setup and maintenance
  • If necessary, configure / development Ease
  • Compatibility
  • Security, Security Update etc.

All tips are welcome, please provide some reasons why you think the solution is good.

I came with .NET and WCF. Developing a thin .NET wrapper for COM objects is easy and WCF gives you soap. You can choose between IIS or self-hosting.

  • License Cost: You need Visual Studio and Windows Server License (for IIS hosting options). NET and WCF runtime are free I
  • Ease of installation and maintenance: Not sure what should be
  • Ease of configuration / development: WCF is very easy to use in development
  • Compatibility: WCF adheres to SOAP and WS- * extensions
  • Security: IIS 7 is safe platform

In the .NET framework To highlight COM components:

About WCF: msdn.microsoft.com/en-us/netframework/aa663324.aspx

In more information (using SOAP) WCF : Msdn.microsoft.com/en-us/library/ms7 31082.aspx

PS: Sorry, this does not allow me to post many hyperlinks


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -