Quick Poll
-
I use all three: Dapper Linq2SQL EF Depends on the project, but the combination is only Dapper+Linq2SQL or Dapper+EF. Much of what I do is highly abstracted, SQL generated on the fly, so Dapper is a godsend. And unless I'm doing business logic on something, mirroring the models in C# is just stupid, in my opinionated opinion. :laugh:
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkMarc Clifton wrote:
Dapper Linq2SQL EF
We use these 3 as well in our shop.
-
I use all three: Dapper Linq2SQL EF Depends on the project, but the combination is only Dapper+Linq2SQL or Dapper+EF. Much of what I do is highly abstracted, SQL generated on the fly, so Dapper is a godsend. And unless I'm doing business logic on something, mirroring the models in C# is just stupid, in my opinionated opinion. :laugh:
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkQuote:
... in my opinionated opinion.
Hey, if you're going to have an opinion, that's the only kind to have! :laugh:
I have lived some thirty years on this planet, and I have yet to hear the first syllable of valuable or even earnest advice from my seniors. -- Henry David Thoreau Ok Boomer. -- Anonymous Millenial
-
Quote:
... in my opinionated opinion.
Hey, if you're going to have an opinion, that's the only kind to have! :laugh:
I have lived some thirty years on this planet, and I have yet to hear the first syllable of valuable or even earnest advice from my seniors. -- Henry David Thoreau Ok Boomer. -- Anonymous Millenial
How come
opineis similar to a tree andopinionis similar to an onion? -
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I don't use either these days, but I haven't touched anything .NET related in like 7 years. Seems like forever. Nothing against them. These days I'm in the Node ecosystem.
Jeremy Falcon
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Neither: I use SQLConnector, SQLCommand, and Reader / Adapter and DataTable as necessary.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
How come
opineis similar to a tree andopinionis similar to an onion?Slacker007 wrote:
opinion is similar to an onion
Or similar to just winging it.
-
Neither: I use SQLConnector, SQLCommand, and Reader / Adapter and DataTable as necessary.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
IDbConnection, IDbCommand, IDataReader, IDbDataParameter, DataTable, DataView. I can use any database system which provides an ADO.net provider/connector (and preferably SQL-92). By the same token, I can implement a class which is not a database but which provides an IDataReader. No adapters, I stopped using those years ago; too much trouble. If I recall correctly, the biggest issue I had with an adapter was that it implements concurrency protection (I may have that wrong) which can't be configured off and every once in a while an update would fail because of it -- when in fact having two updates for one record in the same batch was perfectly fine for the particular situation. So I stopped using them and never looked back.
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I use Linq-to-SQL for SQLite in a couple of projects and EF on a couple, I guess depends on the project.
Give me coffee to change the things I can and wine for those I can not! PartsBin an Electronics Part Organizer - An updated version available! JaxCoder.com Latest Article: Simon Says, A Child's Game
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I don't have more than a vague idea of what you're even talking about. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Have not used this myself, but it looks interesting: Linq To DB[^] It supports popular databases like MS Access, MS SQL Server, PostgreSQL, MariaDB, SQLite, Firebird, DB2, Informix and Oracle.
Interesting
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Neither. Using Dapper or SQLCommand, Reader.
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Isn't LINQ To SQL ancient history? :~ I'm using the latest versions of EF myself. Code first and migrations for automatic deployment.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Never neither. I just use straight ADO.net for access to whatever database system I need to connect to. If I understand correctly, those connect only to SQL Server. Using ADO.net allows an application to connect to multiple database systems, even allowing the user to specify which at run time if the application is written that way.
PIEBALDconsult wrote:
If I understand correctly, those connect only to SQL Server.
You understand incorrectly then. EF uses ADO.NET under the hood and also supports SQLite, MySQL, PostgreSQL, Azure Cosmos DB, Firebird, Oracle...
PIEBALDconsult wrote:
Using ADO.net allows an application to connect to multiple database systems, even allowing the user to specify which at run time if the application is written that way.
How often is that a requirement? :~
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Never used either, I don't mind writing the code myself.
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Kevin Marois wrote:
Linq-To-SQL versus Entity Framework
Neither. It's usually sqlclient unless I have to target non-sql server, then it's ado.net. I use datareaders or adapters to fill datasets/datatables. CRUD statements are all hand-rolled.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
PIEBALDconsult wrote:
If I understand correctly, those connect only to SQL Server.
You understand incorrectly then. EF uses ADO.NET under the hood and also supports SQLite, MySQL, PostgreSQL, Azure Cosmos DB, Firebird, Oracle...
PIEBALDconsult wrote:
Using ADO.net allows an application to connect to multiple database systems, even allowing the user to specify which at run time if the application is written that way.
How often is that a requirement? :~
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I do not use either for Database data, Entity Framework has always had bugs and a lot of overhead that is not necessary in the name of convenience. LINQ is actually awesome with arrays and datsets but not for database query functions. For MS SQL Db SqlConnector SqlCommand SqlAdapter are best in my opinion. For all others, ODBCConnector ODBC Command and ODBCDataAdapter. MySQL would use MySqlData.DLL data connectors and for Oracle use ODP.net. You get the picture right!
-
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
First off, I try to decouple the data processing from the main code, so that the application is not exposed to the actual query engine used. I tend to use EF as it can get me going quickly. But if there are bottlenecks or other issues I can move to another framework, or go straight to ADO.Net. Optimize where and when necessary. I've just published (with help) a fairly big open-source project on Github, which scans AzDo repos and reports on all kinds of tidbits - things like what version of .Net being used, libraries, NuGet and npm packages, etc. Useful to then determine which apps should be updated, for example if you are using a version of .Net no longer getting security patches. Sorry, rambling a bit. My point is I am considering switching some of this from SQL Server to a non-SQL backend. Easy to manage with all the DB code decoupled.
-
Isn't LINQ To SQL ancient history? :~ I'm using the latest versions of EF myself. Code first and migrations for automatic deployment.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
I never did get the hang of Migrations, always seemed to foul things up. Much prefer creating a DB project and code it directly there. Then again, I grew up using SQL Server and just got used to coding it directly.
