4 ms·
Their NuGet ecosystem is extremely rich. For example, see https://www.nuget.org/packages?q=image+processing https://www.nuget.org/packages?q=image+processing M
by rightos 9y ago
Their NuGet ecosystem is extremely rich. For example, see https://www.nuget.org/packages?q=image+processing https://www.nuget.org/packages?q=image+processing
My experience is that LINQ pretty much beats every other way of interacting with a database I've ever seen.
Core is likely a more restrictive right now - EF Core for example is still in a very weak state, but things are improving and in a few versions I fully expect it to be a solid product.
- jrs95 9y agoEntity Framework is a pretty fantastic ORM. The only thing that's ever come close for me is SQLAlchemy.
- rightos 9y agoEF6, yes, it really is the best thing going. But EF Core right now has some major issues with lazy loading and not supporting group by on the DB-side last I checked. I believe those are both scheduled to be fixed.
- jrs95 9y agoYeah, I wasn't referring to Core -- last time I checked, it wasn't quite there yet. I don't think it ought to be much longer, though.
- ajryan 9y agoLINQ 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.
- dep_b 9y ago> My experience is that LINQ pretty much beats every other way of interacting with a database I've ever seen. Until you're going to do more complex queries over multiple tables.
- pdwetz 9y agoIf you want to interact with the database, in my experience Dapper and real actual SQL statements beat it hands down (both readability and performance). I love utilizing LINQ aside from that (e.g. creating custom comparison methods/classes and using it's baked in set operations for comparing/contrasting multiple collections).