4 ms·
LINQ to SQL is a dead end. Look into LINQ to DB https://github.com/linq2db/linq2db https://github.com/linq2db/linq2db which is way faster than LINQ to SQL ever
by pbz 8y ago
LINQ to SQL is a dead end. Look into LINQ to DB https://github.com/linq2db/linq2db https://github.com/linq2db/linq2db which is way faster than LINQ to SQL ever was (faster than even Dapper). If you must you could give EF a try, but stay away from LINQ to SQL.
- CuriousSkeptic 8y agoThe value of Dapper IMHO is not the speed. It is precisely the interface. With dapper I can copy paste code between C# and SQL contexts freely. Exploring the database directly in SQL and then use the result directly in the program without a translation step.
- naasking 8y agoLINQ to DB has always seemed interesting, but I don't like it's use of attributes for POCO properties. It's not clear from the introduction whether non-attribute properties will work if the names and types are compatible, or even if the attributes are custom or come from the standard System.ComponentModel.DataAnnotations. The attributes aren't discussed at all in the introductory examples actually.