Today at the SDP I gave a lecture on the different ways we can communicate with the web from Silverlight 4. We talked about the different HTTP Stacks Silverlight offers and the many communication types & technologies you can use, such as:

• Simple http requests
• Restful services
• Syndication (Rss/Atom) feeds
• ASMX Web Services
• WCF services
• WCF Data Services
• TCP communication
• UDP communication

Yes, you can do all the above with Silverlight 4 !

In addition, we talked about different WCF scenarios that you can achieve in Silverlight 4, such as:

• Binary message encoding
• Catching SOAP Faults
• Passing HTTP & SOAP Headers
• Authentication
• Using Duplex

You can download the presentation and the code samples from here.

The lecture’s recording will be available from the SDP site in a few days, so stay tuned…

Just finished passing my presentation about ORM & Entity Framework basics

This presentation is part of a whole-day seminar about ORM Tools & Concepts

Currently Bernie & Erez are demonstrating NHibernate & Entity Framework head-to-head and later on Gil will deep dive into Entity Framework and Erez & Bernie will once again join forces to talk about Data Access Pattern in the real world.

We’ll finish the day with an Expert Panel, where Oren Eini will join us to talk about ORMs, NHibernate, Entity Framework, Pattern, Tips & Tricks and more.

Be sure to download the presentation from our blogs. Video recordings will be available after the SDP.

In the past, when we tried to connect from Silverlight 2 to WCF Services that threw exceptions (every now and then), we got the famous “Not found” Communication Exception.

The reason we didn’t get a SOAP Fault is that WCF returns SOAP Fault responses with a HTTP code of 500 – this is according to SOAP protocol, but the browser doesn’t allow 500 responses to be returned to Silverlight – it replaces them with a CommunicationException and thus hides the real fault that returned.

When we moved to Silverlight 3, Microsoft published the following article, describing how to workaround the browser’s block, using a Message Inspector in the WCF-side to replace HTTP 500 fault responses with a HTTP 200 fault responses, thus allowing Silvelright to get these messages.

But… this fix will make your WCF service not compatible with the SOAP protocol, not mentioning you’ll have a whole new inspector to manage (test, debug, maintain…), and you’re debug skill will need to improve (try using fiddler to find these errors when the return code is 200 and not 500 – no red lines !!).

There is another solution that isn’t discussed much, and doesn’t require making any changes in WCF – changing the HTTP Stack Silvelright uses for the services.

In Silverlight 3 a new HTTP Stack was released – the Client HTTP Stack. The Client Stack uses the OS directly to create network operations, instead of using the browser. The new stack can be used instead of the Browser’s HTTP Stack for http and https. There are some differences between the stacks, one of them being the Client’s stack ability to handle all types of responses, including HTTP 500 responses.

To use the Client Stack for a specific service, just add the following code at the beginning of your Silverlight application (just change the url):

HttpWebRequest.RegisterPrefix(http://localhost/services/serviceX, 
WebRequestCreator.ClientHttp);

You can read more about the ClientHttp class here, or just come to the SDP (registration required), where I will talk about the Client stack and other changes made in Silverlight 3 & Silverlight 4 that improves Silverlight’s ability to use network resources.

There are going to be many cool stuff in the SDP lectures, straight from the PDC, I myself still haven’t decided which lectures to go to (WCF 4? ASP.NET 4? WF? many to choose from).