Share via


WCF, HTTP, Security and Data Service topics for Silverlight

Our team has been watching the forums and there are a lot of questions regarding using Silverlight with WCF and data services, HTTP questions and security questions. We created some new topics and updated existing topics to better cover these areas for the Silverlight 2 release, however it would appear that most folks haven't found these topics. Here are some links:

  • HTTP Communication and Security with Silverlight covers pretty much what the title says it does; Silverlight HTTP capabilities and security considerations.
  • Accessing Web Services in Silverlight contains links to a bunch of topics on WCF services, including more security
  • Security contains links to topics that cover application security, HTTP security and sockets security. This topics contains many of the same links you'll find in the other two, but we wanted to make this info discoverable in one location.
  • ADO.NET Data Services contains links to topics on building Silverlight applications that communicate with ADO.NET data services.

Please take a minute to check out these topics and provide feedback to us in the form of MSDN ratings and comments.

Thanks

--Cheryl

Comments

  • Anonymous
    November 11, 2008
    PingBack from http://www.tmao.info/wcf-http-and-security-topics-for-silverlight/

  • Anonymous
    November 12, 2008
    Many of us have been struggling to create business-oriented (LOB) forms using Silverlight 2 and ADO.NET

  • Anonymous
    November 12, 2008
    In this issue: Silverlight Girl, Mehdi Slaoui Andaloussi, David Anson, Cheryl, Justin Angel, Kathy Kam

  • Anonymous
    November 13, 2008
    The comment has been removed

  • Anonymous
    December 02, 2008
    Kellen, Thanks for your comment. I checked with the team responsible for the sockets implementation and there are valid security reasons for the restrictions you mention. They cannot allow users to make security decisions through prompting because they are concerned about risks to the network, not just the individual client. Cheryl