Search

Yavor Georgiev is talking about web service faults with the new SL3 client HTTP stack.

Carlos, one of our team members, has posted an quick blog post on how to use SOAP faults with the new client HTTP stack, introduced in SL3. This makes configuring faults significantly easier: there is no need to write custom code in your WCF service, and all you need to do is add one line of code to the Silverlight client.

Cheryl Simmons has posted a table that summarizes some of the basic HTTP capabilities of Silverlight 3 and whether browser or client HTTP handling supports the capability.

In previous versions of Silverlight, the browser handled all the HTTP communication for the Silverlight plug-in. The browser HTTP stack works well but has some limitations including the HTTP methods you can use and the response codes that are accepted. In Silverlight 3, you can opt-in to have the Silverlight client perform the HTTP handling. By opt-in, I mean, if you don't specifically choose the client to perform HTTP processing, it will be done by the browser, just like it always has been. However, if you decide you need to call REST services, you can easily do this with Silverlight3 by opting in to the client HTTP stack.

The sample code contains a reusable, standalone JavaScript library (sl3duplex.js) which implements the client side of the polling duplex protocol. The full source code and Visual Studio solution is available for download. Please also check the Silverlight development environment prerequisites.

This sample demonstrates how a Micrososoft Silverlight 3 application can consume asynchronous data notifications from the server using the polling duplex protocol of Windows Communication Foundation (WCF). I am also discussing selected aspects of the implementation, in particular related to performance.

When trying to access a web service, either WCF (.svc) or asmx in Silverlight works well until we add SSL, when trying to access and using fiddler, complains about the clientaccesspolicy.xml by a crossdomain error:

An error occurred while trying to make a request to URI This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services.