Coming soon to LINQ to SQL
LINQ to SQL went gold a few months ago with the release of Visual Studio 2008 and .NET Framework 3.5. It has been somewhat quiet since then – and as we near the launch of Visual Studio 2008, you may be wondering what we have been up to.
Things aren’t so quiet over here on our end, even if it looks that way. The team has been busy adding features so that you will have better support for SQL Server 2008 in the future. Things we’ve been working on include support for new T-SQL data types that are being introduced in SQL Server 2008 – namely DATE, TIME, DATETIME2 and DATETIMEOFFSET, so that you can enjoy the same rich LINQ support and CUD support over data that uses many of the new types that are being introduced in SQL Server 2008.
Watch this blog for more on this as we get closer to releasing some of this functionality!
Faisal Mohamood
Program Manager – LINQ to SQL
Comments
Anonymous
February 21, 2008
PingBack from http://www.biosensorab.org/2008/02/21/coming-soon-to-linq-to-sql/Anonymous
February 21, 2008
Hi this is a great news! Thank you very much!!! We are looking forward for RTM version! We were using previous version and it works just great!Anonymous
February 21, 2008
Wondering when you'll get to use the new SQL 2008 Data Types with LINQ to SQL? Check out a new post byAnonymous
February 21, 2008
Wondering when you'll get to use the new SQL 2008 Data Types with LINQ to SQL? Check out a new postAnonymous
February 21, 2008
Are you planning to add support for the location data types too?Anonymous
February 21, 2008
Faisal Mohamood , the LINQ to SQL Program Manager, has posted about the work his team has been doingAnonymous
February 22, 2008
Faisal Mohamood vient d'annoncer le support des nouveaux types de SQL Server 2008 : DATE, TIME, DATETIME2Anonymous
February 22, 2008
Check it out, on the ADO.NET Team blog Faisal Mohamood, a PM on the LINQ to SQL team, posted on the newAnonymous
February 22, 2008
It's funny when you work at a company that has as many small projects as it has big ones. I hear oneAnonymous
February 22, 2008
Check it out, on the ADO.NET Team blog Faisal Mohamood, a PM on the LINQ to SQL team, posted on the newAnonymous
February 22, 2008
Spacial data type support will be my favourite. I wonder what namespace/assembly these new .net data types will be added toAnonymous
February 23, 2008
When is this slated for? Charlie Calvert says "next release", but what is the defintion of that? SP1? The next version of Visual Studio? Something else? Thanks JulieAnonymous
February 23, 2008
Something to keep in mind that may not have been clear from the post above is that while LINQ to SQL will have support for some of the new SQL Server 2008 types. It won't, unfortunately, support the new spatial data types. That's something which will have to come at a later time.
- Danny
Anonymous
February 24, 2008
Linq to SQL is one of the greatest achievements ever to come out of Redmond.Anonymous
February 24, 2008
I'm assuming this means that the designer will support SQL 2008 (minus the spatial data types) as well.Anonymous
February 24, 2008
Suite à l'annonce faite pour LINQ To SQL , Julie s'est posée la question de ce qu'il en était pour l'EntityAnonymous
February 26, 2008
Great news Linq to Sql will soon support the SqlServer 2008 data types! Will there be also improved tools for Linq to Sql? Like the model designer that can update the dbml-file when there were changes to the database? PeterAnonymous
February 26, 2008
Quite a bit of activity last week in the Visual Studio and ORM spaces. Visual Studio released a CTP ofAnonymous
February 27, 2008
Support for CLR UDT's would be good.Anonymous
February 28, 2008
Faisal Mohamood, PM for LINQ to SQL, discusses upcoming changes to LINQ to SQL in this blog post . "ThingsAnonymous
February 28, 2008
The comment has been removedAnonymous
March 03, 2008
Will the LINQ to SQL designer support updating the dbml file when the schema changes? Currently, my project is getting to the point were the LINQ to SQL designer will become unusable without this feature. :-(Anonymous
March 07, 2008
@Kevin.... I agree, schema changes seem a weak point in the designer support.Anonymous
March 13, 2008
Support for schema changes unfortunately didn't make it into the first release of LINQ to SQL. It certainly is among the features we are hoping to add for LINQ to SQL - but at this point it is too early to tell when it will be available. -FaisalAnonymous
March 21, 2008
Please add a better way to no nolockAnonymous
March 24, 2008
Hello, Have you heard about a new database synchronization tool Datbase Restyle (http://www.perpetuumsoft.com/Product.aspx?lang=en&pid=55) that supports LINQ To SQL object model and allows automatic synchronization if LINQ To SQL object model with your live database? Probably, this tool will be helpful.Anonymous
March 25, 2008
Any word on support for the XML Datatype?Anonymous
March 27, 2008
This product supports XML Datatype as well. You should just try it. Kate.Anonymous
May 29, 2008
It does not support XML Datatype-based queries, though. All you can do is retrieve the XElement in the loaded result set, but not specify a LINQ 2 XML (or XQuery, which is supported by SQLServer 2005+) as a filter.Anonymous
August 27, 2008
The comment has been removedAnonymous
January 09, 2009
Hi this is a great news! Thank you very much!!!Anonymous
May 08, 2009
how about UDT support for semi-native Sql Types. That being the new spacial stuff. Talk a show stopper. It would be cool if i could just import the binnary as a refrence and then l2sql could use that..Anonymous
May 08, 2009
how about UDT support for semi-native Sql Types. That being the new spacial stuff. Talk a show stopper. It would be cool if i could just import the binary as a reference and then l2sql could use that..Anonymous
June 01, 2009
Check out http://www.codeproject.com/KB/linq/LINQ_to_SQL_Database_Sync.aspx An open source utility that synchronizes your database structure with a LINQ to SQL model.