April 9, 2009 at 10:07 am
I seem to recall a posting or two in the daily email questioning Microsoft's commitment to and the future of LINQ. Today I've been looking at LINQ to XML as a potential way to address one facet of a project I'm working on. LINQ to XML looks promising, but I don't want to start down that path if it looks (to others more knowledgeable than me) as if LINQ will turn out to be yet another Microsoft blind alley. I'm not flaming MS; but we all know many of their "hot" technologies that have withered on the vine. Thanks in advance for candid advice from those in the know.
April 16, 2009 at 9:21 am
LINQ is not going anywhere but the LINQ to XML will be dependent on people using it and giving feedback to Microsoft because XML is in ANSI without basic relevant math, so Microsoft is implementing only as needed. This is one place I agree with Microsoft so the problem is not Microsoft be rather politics in standards. If you implement it and run into issues you could migrate it to the Entity Framework, the only base requirement if I remember correctly is to use Views instead of stored procedures. Check the docs for the current requirements so you could just swap out Data Access as needed.
Kind regards,
Gift Peddie
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply