The client endpoint configuration consists of an absolute address for the service endpoint, the binding, and the contract, as shown in the following example. Like the service, the client uses a configuration file (App.config) to specify the endpoint with which it wants to communicate. Svcutil.exe /n:"" /l:vb /out:generatedClient.vbīy using the generated client, the client can access a given service endpoint by configuring the appropriate address and binding.
To generate client in Visual Basic type the following from the SDK command prompt: Run the following command from the SDK command prompt in the client directory to generate the typed proxy: svcutil.exe /n:"" /out:generatedClient.cs The hosted service must be available to generate the client code, because the service is used to retrieve the updated metadata. This utility retrieves metadata for a given service and generates a client for use by the client application to communicate using a given contract type. This generated client is contained in the file generatedClient.cs or generatedClient.vb. The client communicates using a given contract type by using a client class that is generated by the ServiceModel Metadata Utility Tool (Svcutil.exe). As such, the service turns on the ServiceMetadataBehavior and exposes a metadata exchange (MEX) endpoint at The following configuration demonstrates this. The framework does not expose metadata by default. For clients on remote computers to access the service, a fully-qualified domain name must be specified instead of localhost. The contract is the ICalculator implemented by the service.Īs configured, the service can be accessed at by a client on the same computer. The binding is configured with a standard WSHttpBinding, which provides HTTP communication and standard Web service protocols for addressing and security. The service exposes the endpoint at the base address provided by the IIS or WAS host. The service exposes an endpoint for communicating with the service, defined using a configuration file (Web.config), as shown in the following sample configuration. Public double Divide(double n1, double n2) Public double Multiply(double n1, double n2) Public double Subtract(double n1, double n2)
Public class CalculatorService : ICalculator Service class that implements the service contract. Public Function Divide(ByVal n1 As Double, ByVal n2 As Double) As Double Implements ICalculator.Divide Public Function Multiply(ByVal n1 As Double, ByVal n2 As Double) As Double Implements ICalculator.Multiply Public Function Subtract(ByVal n1 As Double, ByVal n2 As Double) As Double Implements ICalculator.Subtract
Public Function Add(ByVal n1 As Double, ByVal n2 As Double) As Double Implements ICalculator.Add ' Service class which implements the service contract. The service implementation calculates and returns the appropriate result, as shown in the following example code. ' Define a service contract.įunction Add(ByVal n1 As Double, ByVal n2 As Double) As Doubleįunction Subtract(ByVal n1 As Double, ByVal n2 As Double) As Doubleįunction Multiply(ByVal n1 As Double, ByVal n2 As Double) As Doubleįunction Divide(ByVal n1 As Double, ByVal n2 As Double) As Double The service implements an ICalculator contract that is defined in the following code. The client makes requests to a given math operation and the service replies with the result. The contract is defined by the ICalculator interface, which exposes math operations (add, subtract, multiply, and divide). The service implements a contract that defines a request-reply communication pattern. The service configures a run-time behavior to publish its metadata. The binding specifies transport and security details for how the service is to be accessed. This includes an endpoint definition that specifies an address, binding, and contract. The service and client specify access details in configuration file settings, which provide flexibility at the time of deployment. If you would prefer to get started with a sample that hosts the service in a console application instead of IIS, see the Self-Host sample.
0 kommentar(er)
