/// <summary>Gets the foo</summary>
/// <param name="bar">the bar</param>
/// <returns>the foo</returns>
Foo GetFoo(Bar bar) {
...
}
I'm not saying I've never done it, but I usually end up deleting them later.
/// <summary>Gets the foo</summary>
/// <param name="bar">the bar</param>
/// <returns>the foo</returns>
Foo GetFoo(Bar bar) {
...
}
Binding validation failed because the endpoint listen URI does not represent an MSMQ direct format name. The service host cannot be opened. Make sure you use a direct format name for the endpoint's listen URI.
| Symbian | 166,463.3 | 46% |
| RIM | 69,370.6 | 19% |
| iOS | 50,791.9 | 14% |
| Windows Mobile | 30,596.9 | 8% |
| Android | 22,619.2 | 6% |
| Linux | 17,440.4 | 5% |
| Other | 5,699.6 | 2% |
I spent some time struggling with a WCF service with a .NET MSMQ binding. The public queue resided on a test Windows Server 2003 machine. Everything worked fine on my machine, but when I installed the WCF service on the test server, I got the following error message:
An error occurred while opening the queue: The queue does not exist or you do not have sufficient permissions to perform the operation. (-1072824317, 0xc00e0003). The message cannot be sent or received from the queue. Ensure that MSMQ is installed and running. Also ensure that the queue is available to open with the required access mode and authorization.
The error code (0xc00e0003) corresponds to MQ_ERROR_QUEUE_NOT_FOUND.
Turns out, I needed to reference the queue with net.msmq://server/queue instead of net.msmq://server/public/queue. It's unfortunate the latter URL works in some cases but not others.