This is the Day 10 article. If you have not read the previous articles then please go through the following articles:

Introduction

In this article, we will discuss endpoints which consists of Address, Binding and Contract.
In previous articles, we have seen about ServiceContract, OperationContract, and implementation of these in the service class. In this implementation, we write business logic. Services expose endpoints to the world. There may be multiple endpoints in a service. Endpoints define communication options.
WCF–Address-Binding-Contract.jpg

Endpoint

An Endpoint is a piece of information that tells WCF how to build the runtime communication channels to send and receive messages. An endpoint consists of the three things address, binding and contract.
Endpoint

Address

Address - Where - Where to send messages
An Address is a unique Uniform Resource Locator (URI) that identifies the location of the service. It defines the network address for sending and receiving the messages. It is divided into four parts:
EndPoint Address

Binding

Binding - How - How to send messages
A Binding specifies which transport protocol to use, what message format and which any of the ws* protocols we want to use to a particular endpoint.
BasicHttpBinding
wsHttpBinding
wsDualHttpBinding
webHttpBinding
NetTcpBinding
NetPeerTcpBinding
netNamedPipeBinding
netMSMQBinding

Contract

A Contract provides the additional detail about the structuring contents of the various messages that will be used by the various operations exposed to the particular endpoints. For example we create a service "TopupService", the interface used to define the service is "ITopupService" and the project name is "Utility". The contract for this service would be Utility.ITopupService.
Next >> WCF Service Configuration Using Web.config - Day 11