asp.net - Has Microsoft confirmed their stance on LINQ to SQL end-of-life? -
I am trying to make an educated decision, which I use for porting the ORM to use for many Oracle applications I am responsible for the MVC 2. I have seen that the ORM is from LINQ to SQL, LINQ to units and NHibernate. L2S seemed to be the easiest, but I've got many articles and blog entries that show that Microsoft will no longer be able to update it after .NET 3.5. Keeping this in mind, I am doing a little bit with the institutions, but I think it is cumbersome and more complex for small applications, with whom I am working (with nHibernate). I recently purchased "Pro ASP.NET MVC 2 Framework" by Steven Sanderson, in which he decided to use SQL as his ORM with LINQ:
I know that something Developers have expressed concern that the Microsoft entity could leave SQL from LINQ in favor of the criteria, however, Microsoft increased NQ in NIT 4 to NXL and increased, so these fears flooded Like can not be justified.
I knew that they had made changes, and neither did I care about seeing, because the general community's opinion is that L2S was coming closer to the end-life, L2E
I hope someone has shed some light on the status of SQL from Microsoft's Linux. Dayman Guard wrote about some changes on his blog. In the applications I am porting and updating, there is a lifetime of about 8-10 years, so I like to adopt the technology that will not be left in the time limit and except for my replacement Cree Creek. Please give it. (Of course, if there are any other recommendations for someone's small shops - our database has less than 5 million records - I would love to hear them.)
I'v received message: Hopefully we should actually use the unit framework as possible; SQL is basically in maintenance mode from LINQ: it will not be away at any time soon, but it will not develop quite either. Meanwhile the unit framework is evolving and integrating with other products / frameworks such as RIA services or WCF data services.
Comments
Post a Comment