Yavor Georgiev - Using WCF with Silverlight 3.0

Download this episode

Download Video


WCF (Windows Communication Foundation), provides a clean way to develop connected, service-oriented applications using the .NET Framework. Yavor Georgiev joins us in this episode to show us more about WCF enhancements in Silverlight 3.0, and how it might be able to help you out in your applications.

For some more details on WCF in Silverlight 3.0, you might want to check out this session from MIX09:

And here are a couple more links you might find useful:



Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image

      I'vs not watched this yet, but the data story for Silverlight is already getting messy. Either use WCF, ADO.NET Data Services or the out of band .NET RIA services.

      I know that ADO.NET data services are an abstraction that lies on top of WCF, but where do RIA services fit in? What do they solve that I don't have in WCF?

      Choice is good, but this is already getting confusing.

    • User profile image

      Looks very neat with this new continuous update mechanism.

    • User profile image

      Great job, Iavka!!!

      I wish you all the best and many new materials here with your participation!!!


    • User profile image

      Hi vesuvius - you've nailed the big three ways to get data into yor Silverlight app. Using WCF gives you access to the message exchange pattern and things like how the data is encoded (hence features like duplex and binary), so it's the most flexible and powerful way to do services. Also when you use WCF you are building loosely-coupled and standards based services that can be composed and used by many other clients, not just Silverlight (after all WCF services are standard SOAP 1.2 services).

      ADO.NET Data Services is geared toward a scenario where you want to expose a database as a REST-style service. It is great for that scenario but you are constrained to the serialization formats and message patterns of REST.

      .Net RIA Services is similarly scoped to an end-to-end data-driven solution: you expose a data and bind it to a rich Silverlight control in very few steps. The "service" and "client" are very tightly coupled but you get features such as validation, paging, conflict management, batching, offline support, etc. Again you get great value if you are implementing this kind of scenario, but you lose the flexibility WCF gives you.

      So I think all three approaches have great use cases, but we probably could do a better job of explaining what to use when Smiley


    • User profile image

      That does clear things up a bit, thanks.

    • User profile image

      A change I would like to see with Channel9 is this: Post a link to any samples in the videos so we can download and learn from the example (Please no links to some other page that we have to scan for the download).   If the sample is some not-yet-released preview then a Statement like: "Sample not available"  would be nice.  In anycase, help us get to the samples as fast as possible.

    • User profile image


      ADO.NET Data Services

      .Net RIA Services


      Which one of the above three should I use if my data source is xml and I just want to use Silverlight for data entry?




    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.