An update to our "Using ADO.NET Data Services" whitepaper is now available to match the bits just released with the .NET Framework 3.5 SP1. You can find the paper on MSDN here: https://msdn.microsoft.com/en-us/library/cc907912.aspx. The document is intended to be a good way to go from 0 to 60 with data services and touches on many aspec...
As an offshoot of the feedback we got from different channels , ( Blogs , Direct emails to team members , our discussion forums, etc) we are releasing an “interim build” of the data services Silverlight client which works with the Silverlight 2 Beta 2 runtime ,and works with the RTM ADO.NET Data Services Server released as part of .Net ...
We have started creating a "How do I" video series for data services. A couple videos are already posted here: https://msdn.microsoft.com/en-us/data/cc300162.aspx. We have a number of ideas for future videos and a few more yet to publish, but if you have ideas for videos you would like to see please do let us know. Mike Flasko AD...
Marcelo has a nice post detailing how to deal with a couple common cases that can cause 400 responses from a data service. Check it out here: http://blogs.msdn.com/marcelolr/archive/2008/04/01/fixing-400-bad-request-replies-from-asp-net-when-using-ado-net-data-services.aspx Mike Flasko ADO.NET Data Services, Program Manager
A few folks have asked about using the Silverlight Beta 2 client library against a data service created using the recently released .NET Framework 3.5 SP1 RTM bits. In general, the Silverlight Beta 2 data services library was created to target the .NET Framework 3.5 SP1 Beta release of ADO.NET Data Services server side components. Whil...
ADO.NET Data Services (aka “Project Astoria”) has Released! Today marks the official RTM of Visual Studio 2008 SP1 and the .NET Framework 3.5 SP1, and we are thrilled to announce the official RTM of the ADO.NET Entity Framework and ADO.NET Data Services. You can find more information and download SP1 at https://msdn.microsoft.co...
In some of our past posts, we've discussed one of the benefits of data services is that the interface to such a service is uniform. This means that how you interact with each service (issue a query, insert a new entity, etc) is the same across all services regardless of the schema being exposed. This uniform interface leads to one of th...
Are you at TechEd this week? If so, we have a few Astoria related sessions going on. If you are at the event and want to chat about Astoria, drop me a note or swing by one of the sessions: 6/4 8:30am-9:45am ADO.NET Data Services for the Web (aka "Project Astoria") by M...
We have received a lot of questions lately about how to authenticate calls to an ADO.NET Data Service. Mike Taulty has created a nice post outlining some of the options for authenticating calls to data services. Check it out here: https://mtaulty.com/CommunityServer/blogs/mike_taultys_blog/archive/2008/05/27/10447.aspx -Mike Flas...
So far Astoria has used “merge” semantics for update. That is, an “update” operation (an HTTP PUT request) replaces the values of the properties for the target entity that are specified in the input payload; this applies both to properties and links. If a property or link is not present in a PUT operation, it means “leave it with its current value”...
