April, 2010

As part of Silverlight 4, developers can now use the NetTcp framing protocol for their web services. This is an addition that we expect a lot of you will find useful. However, many of you will probably hit the dreaded CommunicationException that lurks...

When shipping a product, there are always a handful of painful issues that we unfortunately cannot fix due to schedule pressure. One thing we can do is blog about these issues early and provide workarounds, so customers don’t have to spend countless hours...

We have blogged and written about this before, but it keeps coming back as a major pain point when customers get started with WCF in Silverlight. Out of the box, exceptions are not propagated from the WCF service to the Silverlight client. Instead, you...

Some developers reported to us they were experiencing StackOverflowException when using SlSvcUtil.exe that shipped with the SL4 SDK. Upon investigation, we discovered that this happens on machines with a system language set to something else than US English...

A new feature in Silverlight 4 is the ability to consume REST/POX (XML) services in a strongly-typed way, using the same programming model as the desktop framework. That includes WebGet/WebInvoke attributes, UriTemplates and body styles. By default, only...

Did you know it is now easier to debug the server side PollingDuplex in Silverlight 4? With the addition of tracing, you can now get a peek at what is happening internally within your service. Traces from PollingDuplex will include information about what...

I’ve been meaning to blog this for a while, but Tim Heuer beat me to it. His post shows how to dynamically change the endpoint definition when switching from staging to production, while still taking advantage of .clientConfig. This could be especially...