Is LINQ in its current state (may CTP) useable to develop with?
-
Monday, January 15, 2007 6:30 PMWas going through alot of threads, but i didnt see any concrete answer to my question. I am about to start development on a server where we in the future would like to use LINQ. Would it be advisable to start using the LINQ may CTP? or are many things destined to change so we would have been just as good, if not better off going with ADO.NET untill the final release of LINQ is available, and then rewrite it to use LINQ?
All Replies
-
Monday, January 15, 2007 8:38 PM If you plan to use LINQ to Objects or LINQ to XML only, I think you can start now with the Orcas CTP from this month.
If you want to use LINQ to SQL, you're better off waiting until the February CTP or the Beta 1 that will come after that. -
Friday, January 19, 2007 9:20 AM
It is abolutly and 100% usabel to DEVELOP with.
Point is it is not usable enough to deploy anything - on top of the legal hassles that you are not allowed to.
But if you for example work on a long term project that may require / take advantatage of LINQ - there is nothing stoppping you from starting now. You may have to make some changes in the future, but that is part of working with early previews.
But it IS usable. It works, it compiles, it is documented good enough to make progress.
