|
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 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.
|
|
|
|
|
What are you using?
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.
|
|
|
|
|
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? 
|
|
|
|
|
More often for me than for others probably.
|
|
|
|
|
Well, still possible using EF.
|
|
|
|
|
|
Imagine you'd learn something new.
|
|
|
|
|
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. 
|
|
|
|
|
Marc Clifton wrote: SQL generated on the fly
I don't do that very often, but I may accept SQL from a script or the command line.
|
|
|
|
|
Marc Clifton wrote: Dapper
Linq2SQL
EF
We use these 3 as well in our shop.
|
|
|
|
|
Quote: ... in my opinionated opinion.
Hey, if you're going to have an opinion, that's the only kind to have!
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 opine is similar to a tree and opinion is similar to an onion?
|
|
|
|
|
Slacker007 wrote: opinion is similar to an onion
Or similar to just winging it.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
I don't have more than a vague idea of what you're even talking about. 
|
|
|
|
|
Neither.
Using Dapper or SQLCommand, Reader.
|
|
|
|
|
Isn't LINQ To SQL ancient history?
I'm using the latest versions of EF myself.
Code first and migrations for automatic deployment.
|
|
|
|
|
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.
|
|
|
|
|
I did SQL Server for years before switching to code-first and Migrations.
Don't want to go back though.
All my "SQL" is C# now, and by extension strongly-typed, in source control and automatically deployed.
It takes some getting used to and there are some gotcha's, but for me, the pros far outweigh the cons.
Even when I have an existing database, I code it like it was code-first.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
