http://blogs.msdn.com/brajens/archive/tags/WCF/default.aspxTags: WCFenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/brajens/archive/2007/04/26/accessing-description-metadata-wsdl-of-wcf-web-service.aspxThu, 26 Apr 2007 14:02:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:2285302Brajendra Singh2http://blogs.msdn.com/brajens/comments/2285302.aspxhttp://blogs.msdn.com/brajens/commentrss.aspx?PostID=2285302http://blogs.msdn.com/brajens/rsscomments.aspx?PostID=2285302WSDL or service metadata is the core for accessing or using any web service. In ASMX web service, browsing WSDL is straight forward. You develop a web service, host inside IIS and then simply browse ASMX file to view WSDL. But things are not the same...(<a href="http://blogs.msdn.com/brajens/archive/2007/04/26/accessing-description-metadata-wsdl-of-wcf-web-service.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=2285302" width="1" height="1">WCFhttp://blogs.msdn.com/brajens/archive/2007/04/23/exception-handling-in-wcf-web-service.aspxMon, 23 Apr 2007 13:04:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:2244361Brajendra Singh9http://blogs.msdn.com/brajens/comments/2244361.aspxhttp://blogs.msdn.com/brajens/commentrss.aspx?PostID=2244361http://blogs.msdn.com/brajens/rsscomments.aspx?PostID=2244361Exception handling in ASMX web services was a painful job. Information was getting lost over wire / serialization; it was tricky to get fault code back and having a strongly type mapping between service raised exception and client consumed exception was...(<a href="http://blogs.msdn.com/brajens/archive/2007/04/23/exception-handling-in-wcf-web-service.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=2244361" width="1" height="1">WCF