Peter Bromberg's UnBlog

Learning the "WCF way to do stuff" that you already know how to do is hard enough - but being able to debug boo-boos and fix them along the way can be an important part of your toolset. Since WCF services can return complete exception detail of a fault back over to the client, an easy way to enable this is to add the debug element: <behaviors> <serviceBehaviors> <behavior name="serviceBehavior" > <serviceDebug includeExceptionDetailInFaults="True" httpHelpPageEnabled="True"/> <serviceMetadata httpGetEnabled="true" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> the <serviceDebug element with the includeExceptionDetailInFaults and optional httpHelpPageEnabled attributes turns on this cool stuff for debugging. So if an exception occurs, it gets marshaled back to the client where you can see it. See here for details . Finally, Nicholas Allen has a wonderful dow...

"There used to be a real me, but I had it surgically removed" -- Peter Sellers I confess I must have either been asleep at the switch, or Microsoft is just throwing so many CTP's and BETAs at us poor slobs that I got sensory overload. At any rate, WCF is here. They actually released it last November, according to Clemens Vasters , last Nov 8th - and its pre-baked into Windows Vista - all this under the moniker of ".NET Framework 3.0". Even some hosting ISP's have already installed it for their customers. OK, so what is WCF (Windows Communications Foundation) and why should I care, right? Let me try to provide a short, meaningful explanation: Do you think it would be useful to you as a programmer if they took ASP.NET Web Services, Web Service Enhancements, .NET Remoting, Enterprise Services, and System.Messaging, and rolled them all into this new integrated architecture, programming model, and runtime environment and provided a more productive SOA developmen...