| Start |
|---|
| Getting started sample The service describes the operations it performs in a service contract that it exposes publicly as metadata. The service implementation calculates and returns the appropriate result, as shown in the following example code. The service exposes an endpoint for communicating with the service, defined using a configuration file (Web.config), as shown in the following sample configuration. The framework does not expose metadata by default. As such, the service turns on the ServiceMetadataBehavior and exposes a metadata exchange (MEX) endpoint at http://localhost/servicemodelsamples/service.svc/mex (opens new window). The following configuration demonstrates this. The client communicates using a given contract type by using a client class that is generated by the ServiceModel Metadata Utility Tool (Svcutil.exe). Run the following command from the SDK command prompt in the client directory to generate the typed proxy: Like the service, the client uses a configuration file (App.config) to specify the endpoint with which it wants to communicate. The client endpoint configuration consists of an absolute address for the service endpoint, the binding, and the contract, as shown in the following example. The client implementation instantiates the client and uses the typed interface to begin communicating with the service, as shown in the following example code. |
Read Article
https://develop.horje.com/learn/1434/reference