MSMQ reports many common errors using generic error messages. For example, opening a queue might give you an error message that looks like this. 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.

One concept that sometimes confuses ASP.NET developers when moving to WCF is the notion of session state. In ordinary WCF services, all of the session state is stored in local volatile memory. The application has to choose to copy over a portion of the session state to a durable storage location for that state to be preserved across running instances. WCF doesn't come with a built-in option for enabling persistent storage of session state or enabling access to the session state from other processes.

Security and streaming are two features that often do not get along with each other. Although the concepts are not inherently in conflict, their implementations often do things that cause problems for the optimal execution of the other. You may have seen that the message security channel, like the reliable messaging channel, in its native mode likes to buffer messages. This is because signing is one of the aspects of message security. The message signature is typically computed based on the contents

Distributed applications are tricky. The internet is a fickle beast that will lost data at will and run counter to many intuitions. Getting distributed applications to run smoothly and performant at scale is particularly difficult.  There isn’t a single "go fast" silver bullet, rather it’s more of an art. At PDC this year you’ll have [...]

PDC is approaching rapidly and Microsoft is opening up its communication around the next wave of technologies; one thing I believe to be particularly interesting is Codename Dublin . This technology supplements Windows with much needed application platform components to enhance the WCF and WF design experience. Among other things it includes infrastructure services for message correlation and forwarding, content-based routing and transaction compensation. I guess you can look at WCF and WF as frameworks

Matt posted a great description of the WCF (and WF) talks we’re giving at PDC. In particular there are two sessions that I’d like to call out. The first is Ed Pinto’s session, where you’ll find out about the significant investments we’ve made to improve the WCF authoring experience: WCF 4.0: Building WCF Services with WF in [...]

Earlier this week came the official announcement of the .NET Framework 4.0 and the application server role extensions in Windows Server called Dublin. These are the two products that I've been spending most of my time working on lately. .NET 4.0 obviously encompasses new versions of WCF and WF while Dublin extends the server capabilities of IIS and Windows Server for hosting managed service applications. Here are the talks at PDC that are going to directly focus on WCF 4.0, WF 4.0, and Dublin, including

While I wait for the title and abstract of my PDC talk to be updated with the correct content, here is what you can expect. The theme of the talk is obtaining performance and scale from distributed systems built using WCF. The style of the talk is Zen. At the end of the talk you will understand why things work the way they do and how to spelunk the depths of the system. There will be no graphs or benchmarks. The level of the talk is 300 and up . You should be comfortable with distributed service

Nobuyuki Akama has started a series of articles that give a very good introduction to WCF. The first two articles in the series have been posted so far. I like how detailed the examples and explanations are. You usually don't see that level of detail in introductory material. I think that you shouldn't have to wait for the advanced material before seeing how the system works and seeing exactly what happens on the network. Hello World, WCF !! Part 1. WCF に導入されている新たな設計概念 Part 2. Hello World WCF サーバの開発

Whenever I've talked about tracing I've always used the System.Diagnostics trace listeners in the example. However, there's a second tracing system that is much more powerful but much less talked about called ETW (Event Tracing for Windows). ETW is much less talked about because of the way it combines extreme ununsability with a copious lack of documentation. If you can master ETW though, then it can become an extremely valuable tool. ETW is highly performant, can be made very granular, and allows