COM + Web service: Route to XML Web Services (to) 4-Web_Ser through the check box

For simplicity, the preceding examples use VBScript to access Web services. You can also use Visual C +, Visual Basic 6.0, Visual Basic. NET, or C # to write the soap wsdl name object. For example, Visual Basic. NET can also use compiled managed code to access the same object, as shown in the following example:
Imports System
Imports System. Runtime. InteropServices
Module WKOClient
Sub Main ()
Dim WSDLMoniker =
"Soap: wsdl = http: // localhost/CSSoap. Calc. soap? WSDL"
Dim obj as Object
Obj = Marshal. BindToMoniker (WSDLMoniker)
Console. WriteLine (obj. Add (1, 2 ))
End Sub
End Module
VBScript is used to indicate that both hosted and non-hosted clients can access the COM + component published as COM + Web services. In large organizations or applications, it is difficult to convert all parts at a time. COM + Web services allow conversion of some applications into managed code without having to rewrite existing applications immediately.
Example of a simple client activation object (CAO)
The COM + Web Service release on the server releases each component in the form of WKO and CAO, so no additional server configuration is required. The only operation to do on the server is to select the Uses SOAP check box (on the Activation tab of the COM + application properties page) and enter a value in the SOAP VRoot text box, export COM + applications as proxies. The following describes how to export a proxy application:
Right-click the VB6Soap COM + application in the component service management tool and select Export, as shown in figure 2.
Figure 2: Component service management tools