The MsmqIntegrationBinding is intended for use with

existing, already-written native MSMQ applications. The

NetMsmqBinding is a lot better to use but only works if you

have WCF on both ends of the queue. Therefore, one of these

is always the clear choice for your queuing scenario

depending on what's on the other side. There's nothing

stopping you from hosting separate endpoints for each of

these bindings at the same time if you need communication

with both native and WCF clients. However, the two

endpoints need to be kept with separate queues because the

messages are not compatible.