Difference between Bindings :

BasicHttpBinding  : 

• By default security level is none.
• Also support one extra security mode "TransportCredentialOnly" that is not supported by wshttp,tcp,msmq.
• we can't use protection level(sign&encrypt,sign,none) if doesn't change security level from none to other.
• duplex message exchange mode is not supported.
• does not support session, if we change Instance context mode from percall to per session it will also work as per call. 
• we can't use required session mode with this binding(allowed,not allowed, required)
• similar as a asmx service.
• client with older version of .net can use this.(before 3.0)
• use SOAP 1.1 specification
• support http protocol
• support transfermode (streamed,buffered)

WSHttpBinding :

• By default security level is Message(means ws-security specification is used to secure the message, provide end to end security)
• Both client and service should support ws-specification so less interoperability.
• Duplex message exchange mode is not supported by WSHttp binding instead use WsDualHttpBinding.otherwise get error WShttpBinding doesn't support Duplex.
• Support all instance context mode
• We can't use not-allowed session mode with this binding(allowed,not allowed, required)
• Use SOAP1.2 specification.
• Support http protocol
• Does not have transfer mode

NetTcp Binding:

• Default security mode is transport.(ssl of tls is used to encrypt message.point to point security, mediator can read message)
• Duplex message exchange mode is supported.
• Support all instance context mode.
• We can't use not-allowed session mode with this binding(allowed,not allowed, required)
• Support TCP protocol so used within same network.
• Support transfer mode.

MSMQ :

• Does not support percall message exchange pattern.
• Default transport level security.
• Doesn't support mixed(Transport with message credential) security mode.
• Only binding that support both security mode.

MSMQ allow us to create a program that can reliably send or receive messages over a wire without any loss of message.it uses a queue to store messages in the order in which they arrive.msmq is implemented in the manner that there are multiple clients sending a request to server but because of overload, server is busy processing  previous client requests so in such cases MSMQ can be implemented to maintain a queue of reequests,whenever the server become free it will take requests from queue and process them one by one.

Step1 : Install MSMQ component from windows features on or off
Step2 : Check queue from Administrative tool  -->  Computer management  -->  Service and applications  --> messagequeuing

Step3 :Create queue on host application programatically
string muqueue="D:\\RahulQ";
if(!MessageQueue.Exist(myqueue))
{
MessageQueue.Create(muqueue,false); false means non transaction queue.
}

host.Open();


Step4: App.config changes

<bindings>
 <binding name="msmq" exactlyOnce="false">
 <security mode="none"/> // for remote address of queue

<endpoint binding="netMsmqBinding">


Make multiple calls from client and close host console.
check queue , u will get messages there .
run host console, message will be served and remove from queue.

Named Pipe :
Only support transport security level.
Used if service and clients are on same machine.