Devang Gandhi

Here’s an article that explains what WAS hosting is and how is it different in IIS 7.5 (i.e. Windows 7).

If you are looking for Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) samples for .NET Framework 4.0 Beta 2, you’ll find them here. It is also a good place to start if you want to learn WCF programming.

If you are hosting a WCF service using NetMsmqBinding with Windows Activation Service (WAS) or the MsmqIntegrationBinding on Windows 7, then remember to give “Receive Message” permission to “IIS APPPOOL\DefaultAppPool” on your MSMQ queue.

While developing a WCF service, I had to write a client for it as well to debug/test it. I recently found out that Visual Studio tools include a WCF test client. It is a GUI tool that enables users to test their WCF service by passing parameters to it and viewing the response. It (WcfTestClient.exe) is located at C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\

If you are using MSMQ for your asynchronous communication needs then the following resources will be of great help.

1. Motley Queue blog
2. John Breakwell’s blog (guy knows MSMQ like no one else)
3. Queuing in WCF
   

While working on WCF, I came across this error. It occurs due to Http namespace reservations and I believe it only affects Vista and later OS. This article elaborates steps to resolve this issue.

[Update] This issues does affect older versions of windows and not just Vista. The problem occurs when a service with less privileges is trying to start. It tries to register the URL but since it does not have admin privileges, the OS denies the request. This is called namespace reservation and because of it only a particular group of users have rights to HTTP URL namespace.