<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Eran Nachum's Blog</title>
    <link>http://www.eranachum.com/</link>
    <description>www.eranachum.com - Implementing &amp; executing my thoughts...</description>
    <language>en-us</language>
    <copyright>Eran Nachum</copyright>
    <lastBuildDate>Mon, 11 May 2009 18:18:00 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 1.8.5223.2</generator>
    <managingEditor>eranachum@hotmail.com</managingEditor>
    <webMaster>eranachum@hotmail.com</webMaster>
    <item>
      <trackback:ping>http://www.eranachum.com/Trackback.aspx?guid=f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22</trackback:ping>
      <pingback:server>http://www.eranachum.com/pingback.aspx</pingback:server>
      <pingback:target>http://www.eranachum.com/PermaLink,guid,f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22.aspx</pingback:target>
      <dc:creator>eranachum@hotmail.com (Eran Nachum)</dc:creator>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
      Hi, 
   </p>
        <p>
      as I posted in my previous email in regards Silverlight 2, I’ve decided to use ADO.NET
      Data Services (After consulting my mate Josh Reuben – senior SELA consultant) in order
      to consume the data in a very easy and light way (by using its linq notation and light
      weight data bandwidth using JSON).
   </p>
        <p>
      The only main issue that I encountered with the last few days I am exploring this
      (new for me) technologies is the issue of cross-domain preventing:
   </p>
        <p>
          <em>“ADO.NET Data Services does not currently support cross-domain communications.
      Cross-domain communications are supported with standard REST and SOAP services, but
      not with ADO.NET Data Services. …… </em>
          <em>This means that a Silverlight 2 client
      cannot talk to services exposed through ADO.NET Data Services if those services are
      hosted on a different domain than the domain that hosts the Silverlight client application.” </em>
        </p>
        <h6>Quoted from John Papa post <a href="http://msdn.microsoft.com/en-us/magazine/dd569758.aspx#id0080005" target="_blank">here</a>.
   </h6>
        <p>
      Recently I followed up the the Astoria blog team and found that they created a great
      workaround that comes to give a solution for this issue that holt me these days using
      these data services because my application is distributed and need to be separated
      for a client and server.
   </p>
        <p>
      Find it <a href="http://blogs.msdn.com/tom_laird-mcconnell/archive/2009/03/25/creating-an-ado-net-data-service-proxy-as-workaround-for-silverlight-ado-net-cross-domain-issue.aspx" target="_blank">here</a>. 
   </p>
        <p>
      The Astoria blog team is <a href="http://blogs.msdn.com/astoriateam/default.aspx" target="_blank">here</a>.
   </p>
        <img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22" />
      </body>
      <title>ADO.NET Data Services and Silverlight 2 Application Cross-domain Solution</title>
      <guid>http://www.eranachum.com/PermaLink,guid,f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22.aspx</guid>
      <link>http://www.eranachum.com/PermaLink,guid,f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22.aspx</link>
      <pubDate>Mon, 11 May 2009 18:18:00 GMT</pubDate>
      <description>&lt;p&gt;
   Hi, 
&lt;/p&gt;
&lt;p&gt;
   as I posted in my previous email in regards Silverlight 2, I’ve decided to use ADO.NET
   Data Services (After consulting my mate Josh Reuben – senior SELA consultant) in order
   to consume the data in a very easy and light way (by using its linq notation and light
   weight data bandwidth using JSON).
&lt;/p&gt;
&lt;p&gt;
   The only main issue that I encountered with the last few days I am exploring this
   (new for me) technologies is the issue of cross-domain preventing:
&lt;/p&gt;
&lt;p&gt;
   &lt;em&gt;“ADO.NET Data Services does not currently support cross-domain communications.
   Cross-domain communications are supported with standard REST and SOAP services, but
   not with ADO.NET Data Services. …… &lt;/em&gt;&lt;em&gt;This means that a Silverlight 2 client
   cannot talk to services exposed through ADO.NET Data Services if those services are
   hosted on a different domain than the domain that hosts the Silverlight client application.” &lt;/em&gt;
&lt;/p&gt;
&lt;h6&gt;Quoted from John Papa post &lt;a href="http://msdn.microsoft.com/en-us/magazine/dd569758.aspx#id0080005" target="_blank"&gt;here&lt;/a&gt;.
&lt;/h6&gt;
&lt;p&gt;
   Recently I followed up the the Astoria blog team and found that they created a great
   workaround that comes to give a solution for this issue that holt me these days using
   these data services because my application is distributed and need to be separated
   for a client and server.
&lt;/p&gt;
&lt;p&gt;
   Find it &lt;a href="http://blogs.msdn.com/tom_laird-mcconnell/archive/2009/03/25/creating-an-ado-net-data-service-proxy-as-workaround-for-silverlight-ado-net-cross-domain-issue.aspx" target="_blank"&gt;here&lt;/a&gt;. 
&lt;/p&gt;
&lt;p&gt;
   The Astoria blog team is &lt;a href="http://blogs.msdn.com/astoriateam/default.aspx" target="_blank"&gt;here&lt;/a&gt;.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=f11bff90-b37c-46f6-a4d2-0ecb1eeeeb22" /&gt;</description>
      <category>Silverlight 2;ADO.NET Data Services (aka Astoria)</category>
    </item>
  </channel>
</rss>