What's the story on the O/R mapper built into Visual Studio 2008 vs LLBLGen? I will be asked shortly to explain this to my managers that will (or won't) be writing the check in the next couple of days.

I've been searching the net, but can't find any good informatoin. It seems that I recall hearing that Linq will only work with MS SQL Server, but I could be wrong.

TIA

No, you are not wrong. Here is my list of showstoppers: http://cs.rthand.com/blogs/blog_with_righthand/archive/2007/10/06/LINQ-to-SQL-showstoppers.aspx You should definitely stick with LLBLGenPro. Note that there is another ORM comming from MS (better than LINQ to SQL): Entity Framework sometime next year.

We'll add linq support in our upcoming v2.6 version. So you'll be able to use Linq (which is the C#/VB.NET language extension) with llblgen pro without problems.

Thanks for the info and for the link. Very helpful!

mihies wrote:

No, you are not wrong. Here is my list of showstoppers: http://cs.rthand.com/blogs/blog_with_righthand/archive/2007/10/06/LINQ-to-SQL-showstoppers.aspx You should definitely stick with LLBLGenPro. Note that there is another ORM comming from MS (better than LINQ to SQL): Entity Framework sometime next year.

EF could be quite something since Alex James got involved. He is the guy behind Base4

EF could indeed on paper be great. The thing is that despite the large group of smart people working on it (> 150 people), there's an even larger group of people managing them, and unfortunately for MS, these people have the final say...