3 ms·
LINQ to SQL is pretty poor in my opinion, plus it's no longer maintained and bugs aren't fixed[0]. [0]: http://www.aidanjryan.com/blog/2012/08/25/sqlmetal-bug-
by ajryan 9y ago
LINQ to SQL is pretty poor in my opinion, plus it's no longer maintained and bugs aren't fixed[0].
[0]: http://www.aidanjryan.com/blog/2012/08/25/sqlmetal-bug-with-multi-rowset-stored-procedures/ http://www.aidanjryan.com/blog/2012/08/25/sqlmetal-bug-with-...
- barake 9y agoEntity Framework replaced LINQ to SQL years ago - it’s had multiple major revisions, and two major revs of the .NET Core version. The initial version in 2008 was a total mess. It wasn’t until a few years later that the XML definition and code generation junk was removed and it became useable.
- TheWiseOne 9y agoLINQ to SQL has been abandoned for a long time (since they introduced Entity Framework) but there are a ton of other ORM/DB access tools like Dapper, Massive, PetaPoco, linq2db, nHibernate, Insight.Database, OrmLite, LLBLGen Pro, etc.