New version CTP of ADO.NET Data Services v1.5 is now available

ADO.NET Data Services (aka Astoria) has now the CTP2 release for version 1.5 available that will have the following new features:

  • Projections, the possibility of getting only the columns chosen instead of retrieving all the columns. With this we have now a new set of expressions to provide this ability on the URI.
  • DataBinding, Simplification of the DataBinding for Silverlight and WPF, because using the DataServiceCollection class we can bind it directly to the Data Service.
  • Row Count, Ability to determine the number of elements in a set of entities without having to retrieve them all.
  • Feed Customization, Possibility to customize the way the feed is created instead of using only the default AtomPub version.
  • Server Driven Paging, Provides the ability to define the number of elements retrieved by a request, and also the server will provide a link to the Next and Previous results page.
  • Enhanced BLOB support, enable data services to stream arbitrarily large BLOBs, store binary content separate from its metadata, easily defer the loading of BLOB content when its metadata is requested, etc.
  • Request Pipeline, Possibility to handle the several events that occur during the Request because in the version we have access to a complete set of Request Level Events.
  • New Interface for Custom Providers Writer, New model to develop Custom Providers for ADO.NET Data Services, like here.

You can download it here, and to know more about the subject, read this post about this by the Product Team.

2 thoughts on “New version CTP of ADO.NET Data Services v1.5 is now available

  1. I am keen to understand how your BLOB support is working in the new CTP is there any examples and or demonstration of how to use and where to use this technology

  2. Hello Mike,

    In the download url presented in the post there is a DataServicesCTP2Reference.chm file and if you search for BLOB, you get the following “(…) ADO.NET Data Services enables you to access binary large object (BLOB) data as a data stream. Streaming defers the loading of binary data until it is needed, and the client is able to more efficiently process this data. In order to take advantage of this functionality, the data service must implement the IDataServiceStreamProvider provider. For more information, see Data Services Providers (ADO.NET Data Services). When streaming is enabled, entity types with binary properties are returned without the binary data. Use the GetReadStream method of the DataServiceContext class to access the data stream for the binary data from the service. Similarly, use the SetSaveStream method to add or change binary data for an entity as a stream. (…)”

    And also you can have more information regarding samples and how-to’s here (

Leave a Reply

Your email address will not be published. Required fields are marked *