COM + Web service: Routing to XML Web services by check box 4

services|web|xml| check box for simplicity, the examples above all use VBScript to access Web services. The SOAP WSDL moniker can actually be written using Visual c+, Visual Basic 6.0, Visual Basic. NET, or C #. 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/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 managed and unmanaged clients have access to COM + components that are published as COM + Web services. In large organizations or applications, it is difficult to transform all parts at once, and COM + WEB services allows a subset of applications to be converted to managed code without having to completely rewrite existing applications immediately.

Simple client-activated object (CAO) example
COM + Web Service Publishing on the server publishes each component as Wko and CAO in two forms, so no additional server configuration is required. The only action to do on the server is to export the COM + application as an agent after you select the Uses soap check box (on the Activation tab of the COM + Application property page) and enter a value in the SOAP VRoot text box. The steps necessary to export the agent application are shown below:

Right-click the vb6soap COM + application in the Component Services Administration tool and select Export, as shown in Figure 2.


Figure 2: Component Services management tools