WebServicesClientProtocol Class

Specifies the class from which client proxies derive when using the Web Services Enhancements (WSE).

Namespace: Microsoft.Web.Services3
Assembly: Microsoft.Web.Services3 (in microsoft.web.services3.dll)

Dim webServicesClientProtocol1 As New WebServicesClientProtocol()

public class WebServicesClientProtocol : SoapHttpClientProtocol
public class WebServicesClientProtocol extends SoapHttpClientProtocol
public class WebServicesClientProtocol extends SoapHttpClientProtocol

When you build an XML Web service client, whether you use Visual Studio or not, a proxy class is generated to communicate with the XML Web service. When you are using Visual Studio, that proxy class is generated when a Web reference is made or updated. If the .NET Framework SDK is used without Visual Studio, the proxy class is generated using the Web Services Description Language tool (Wsdl.exe). Either way, the proxy class derives from SoapHttpClientProtocol by default. To use the functionality of the WSE, change the class that the proxy class derives from to WebServicesClientProtocol.

This class provides access to the SoapContext for both SOAP requests and SOAP responses for XML Web service clients with the RequestSoapContext and ResponseSoapContext properties respectively. This SoapContext provides access to the contents of SOAP headers that are defined in the WS-Security and WS-Addressing specifications.

If an instance of the WebServicesClientProtocol is cast or converted to SoapHttpClientProtocol, then the values of all properties of this class that are not members of the SoapHttpClientProtocol are lost. This includes the RequestSoapContext and ResponseSoapContext properties.


Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Development Platforms

Windows XP Home Edition, Windows XP Professional, Windows Server 2003, Windows 2000, Windows 2000 Server, Windows 2000 Advanced Server

Target Platforms