Friday, April 5, 2013

Working with Microsoft WCF


In working with the Microsoft .NET WCF Services it does require a bit of a learning curve, along with trial and error.  Here are some of my notes on the topic:
  • I found it works best to create my WCF Service stand-alone with a new WCF Service Library.  That way I could use the WcfSvcHost from F5 to unit test the Service before including it on my SilverLight application.
  • I open the IIS manager and select the top level web site, then perform a right click "open" to locate the proper place to insert the clientaccessproxy.xml (which I test with a wide open version)
  • I used the WCF Configuration Editor instead of editing the XML by hand.  However, for some reason the WCF Editor doesn't always appear in the right click context menu for the *.config file.  In those cases, I had to actually go to the "tools" menu and specifically select the WCF Editor, then simply close it.  Afterwards, it appears in the context menu (weird).
  • I had to always remember to update the "Web Service Reference" frequently, as changes to the WCF Service aren't reflected in the Reference.vb/Reference.cs file until an update is performed.
  • DNRTV.com has wonderful videos to help you learn the tricks and techniques for .NET development, including WCF and SilverLight.
  • I would run the debugger from both the client side in the XAML code and on the server side with the .XAP and WCF code.
  • For some reason the MIMETYPE for all the SilverLight file types need to be specified in the root web site.
  • I used the EventViewer and IIS log files quite frequently for debugging.
  • I used the commandline "aspnet_regiis" from the C:\WINDOWS\Microsoft.NET\Framework version folder to verify proper ASP.NET configuration.

No comments:

Post a Comment