Yavor Georgiev

Yavor Georgiev yavorg

Niner since 2009



  • Building Customer Facing Mobile Apps with Microsoft Azure

    Thanks to everyone who attended! Here are the links to my demos:

    1. Getting started - just try the quickstart project in the Azure portal
    2. Offline - based on the sample attached to this tutorial
    3. Auth - download sample here
    4. New Relic - just provision from the Azure store and instrument your own app with the NuGet packages shown in the demo.

    Glad to answer any questions!

  • Windows Phone - Getting Started With Azure Mobile Services (.NET Backend)

    Yikes, we have a documentation hole here. We wanted to protect the help page so just the developer can access it. The username is blank and the password is your application key or master key you can get from the Azure portal for your mobile service.

  • Building Data-centric N-tier Applications with jQuery

    The bits and demo from Brad's talk are available at http://bit.ly/wcfjquery.

  • Silverlight TV 46: What's Wrong with my WCF Service?

    @shaggygi - encoded is not supported in Silverlight at this point. If you don't control the service, you could consider building an intermediary WCF service that serves as a relay between Silverlight and the third-party service.

    If you are interested in updates on WCF support in Silverlight, follow me on Twitter at @digthepony.


  • Yavor Georgiev - Using WCF with Silverlight 3.0

    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