Table 1: solutions supported by the WKO Model
WKO client WKO Server
VB 6.0 or unmanaged C ++ VB 6.0 or unmanaged C ++
VB 6.0 or unmanaged C ++ VB. NET or C #
VB 6.0 or unmanaged C ++ SOAP V1.1 (described in WSDL)
VB 6.0 or unmanaged C ++ Microsoft SOAP (ATL Server, soap tk)
C # Or VB. net soap V1.1 (described in WSDL)
C # Or VB. net vb 6.0 or unmanaged C ++
C # Or VB. net vb. NET or C #
C # Or VB. NET Microsoft SOAP (ATL Server, soap tk)
Microsoft SOAP Toolkit V2.0 VB 6.0 or unmanaged C ++
Microsoft SOAP Toolkit V2.0 C # Or VB. NET
SOAP v1.1 VB 6.0 or unmanaged C ++
SOAP v1.1 C # Or VB. NET
Table 2: solutions supported by the CAO Model
CAO client CAO Server
C # Or VB. NET (early binding) VB 6.0 or unmanaged C ++
VB 6.0 or unmanaged C ++ VB 6.0 or unmanaged C ++
VB 6.0 or unmanaged C ++ C # Or VB. NET
C # Or VB. net c # Or VB. NET
This new COM + Web service applies to the following users:
Microsoft®Visual Basic®6.0 or an unmanaged Microsoft Visual C ++®COM + users of COM + applications (which must be activated through the firewall. (Using SOAP does not exclude access to the same component on the server through DCOM. The client computer can select the Protocol .) For these customers, if you want to use SOAP instead of DCOM, you do not need to change the client and server applications in both the client proxy export and the CAO model. You only need to enable SOAP on the server application, export it as the client proxy, and then install the proxy on the Windows XP computer to be used as the SOAP client.
Fully migrated to companies hosting code on Windows XP and Windows. NET Server. The COM + Web service helps you set remote endpoints at both ends of the connection.
Developers who need to combine and match various services in the above two schemes, as well as developers who write managed server components or hosted client applications with unmanaged server components. In the second case, developers can use the COM + Web service to fully utilize the early unmanaged components before replacing them with managed code.