Answer / niloy roy

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.

In wcf, which contract is used to document the errors occurred in the service to client?

0 Answers  

---

Explain about msmq integration binding?

0 Answers  

---

Which standard binding could be used for a service that was designed to replace an existing asmx web service?

0 Answers  

---

What is transfer security?

0 Answers  

---

Explain data contracts?

0 Answers  

---

---

WCF:Is there an error in the Msmq address the "net.msmq://MyHost/private$/MyQueue"?

4 Answers  

---

What is the windows communication foundation?

0 Answers  

---

what are the ways of hosting a WCF service?

0 Answers  

---

What is the "contract" property of endpoint in wcf?

0 Answers  

---

do you know what is the address formats of the wcf transport schemas? : Wcf data services

0 Answers  

---

Differentiate between datacontractserializr and xmlserializer?

1 Answers  

---

How we can achieve operation overloading while exposing wcf services?

0 Answers  

---