Data Services
Blatant repost alert from the ADO.NET team blog! But important IMHO. The Microsoft data team are looking for help to prioritize future work. Is there a feature that you’ve always wanted to have? Or a bug in VS2010 RC? Then provide feedback directly to the teams at the new Connect site. Including: ADO.NET Entity Framework WCF Data Services Thanks all...
Posted On Wednesday, February 10, 2010 10:50 PM | Feedback (0)
In March 2008 we announced SQL Server Data Services. In October 2008 we renamed it to SQL Data Services, part of SQL Services. In July 2009 we renamed it to SQL Azure Database, part of SQL Azure. Same technology, same team – smarter naming :-) Smarter because people were getting confused between SQL Data Services and ADO.NET Data Services (totally different “things”) and the OS you will use in front of SQL Azure is Windows Azure. I wonder what will happen to .NET Services...
Posted On Friday, July 10, 2009 7:52 AM | Feedback (0)
I gave an update on SQL Data Services at DDD Scotland on Saturday (2nd May 2009). The deck was very similar to this one I gave at DevWeek which is already hosted on Slideshare. The final deck will be on the DDD Scotland site in due course. In the meantime, here are the links: SDS Team Blog http://blogs.msdn.com/ssds SDS MSDN Development Center http://msdn.microsoft.com/e... SDS samples http://blogs.msdn.com/jcurr...
Posted On Tuesday, May 05, 2009 10:57 AM | Feedback (0)
March is a busy month for the ADO.NET Data Services team. They have announced details of version 1.5 which will ship before .NET 4.0 and they have released an alpha of the offline bits they talked about back in October. There is a blog post to accompany this release and for me the following was interesting: Q: Is this technology going to be present in the next version of ADO.NET Data Services and/or Visual Studio? A: No. We are working on two fronts. One is the enhancements we want to make to the...
Posted On Thursday, March 12, 2009 11:26 AM | Feedback (1)
The SDS team have announced their updated plans for SQL Data Services. There are plenty of changes to take in – but it looks to be a very positive step in response to feedback from folks who looked at the current CTP. Essentially SDS becomes a full relational database (SQL Server!) in the cloud which we access using familiar programming models such as ADO.NET and ODBC – you get stored procedures, triggers, views etc. As such it will become fairly trivial to “re-platform” on-premise applications to...
Posted On Tuesday, March 10, 2009 11:02 PM | Feedback (1)
On Monday I gave a session on “Windows Azure and a little SQL Data Services” for the .NET Developer Network in Bristol with the main focus being on storage. Thanks to all those who attended – and I hope to be back in the audience next month :-) The main links I wanted to share were: www.azure.com and specifically the downloads: Windows Azure SDK Visual Studio tools and templates The table sample I showed using StorageClient is available for download along with a walkthrough screencast Code sample...
Posted On Tuesday, March 10, 2009 3:31 PM | Feedback (1)
ADO.NET Data Services 1.0 was released with .NET Framework 3.5 SP1 and early adopters were impressed with the combination of power and simplicity for exposing RESTful web services in front of ADO.NET Entity Framework (or pretty much anything with a bit/lot of work). However, those same early adopters soon created a long wish list of features they would like the team to add. The good news is they (and you) won’t have to wait until .NET 4.0 to see them included. The team has announced that there will...
Posted On Friday, March 06, 2009 9:32 PM | Feedback (0)
This one has come up a few times. LINQ to SQL and LINQ to Entities in V1 do not currently support the newest types added to SQL Server 2008 nor do they support your own User Defined Types. More specifically: LINQ to SQL does not support the hierarchyID, geospatial, table or time types. UDTs are not supported. It does support the new DateTimeOffset , DateTime2, and Date types (NB: I have not tried this and I think it may require SP1) LINQ to Entities does not support hierarchyID or geospatial. I haven’t...
Posted On Wednesday, January 21, 2009 5:21 PM | Feedback (0)
It is great that so many folks have started investigating Data Services and the Entity Framework as a result of the MSDN events we have been delivering. Which does also mean I keep getting asked “Why doesn’t mine work?” kind of questions. The good news is the team did a comprehensive post to help you diagnose your issues
Posted On Wednesday, January 21, 2009 5:19 PM | Feedback (0)
ADO.NET Data Service gives you the ability to do: Read/Write with ADO.NET Entity Framework Read only with LINQ to SQL The reason it is read only for LINQ to SQL is that Data Services needs to object model that it is exposing to implement IUpdatable. LINQ to SQL does not. There is a solution – you need implement IUpdatable for LINQ to SQL. This isn’t necessarily as bad as it sounds – if you can narrow down the implementation to how you are using LINQ to SQL. MikeT had a stab at doing just this back...
Posted On Wednesday, January 21, 2009 5:18 PM | Feedback (0)
Full Data Services Archive