Hey guys, I’m starting a new WinForms project with SQLite as the backend. I’m trying to decide between Dapper and EF Core for the data access layer. The main thing I need is to map C# objects to database rows.
I’ve used plain ADO.NET before, but I think using an ORM would make the code easier to maintain. I’m leaning towards Dapper because it’s simpler and I’m okay with writing SQL. I’ve used SQLAlchemy in Python before, which is kind of like Dapper.
But I’m wondering if there are any big advantages to using EF Core that would make it worth the extra complexity and learning curve. What do you all think? Is Dapper good enough for a small project like this, or should I go with EF Core?
have u considered using linq2db? it’s kinda like a middle ground between dapper and ef core. it’s lightweight but still gives u some orm features. might be worth checkin out for ur project. what made u choose sqlite over other options? just curious about ur setup!
For a small SQLite-based WinForms app, Dapper is likely the better choice. It’s lightweight, fast, and gives you more control over your SQL queries. Since you’re comfortable writing SQL and have experience with SQLAlchemy, Dapper will feel familiar and won’t introduce unnecessary complexity.
EF Core is powerful but can be overkill for simple projects. It has a steeper learning curve and might introduce performance overhead you don’t need. Dapper’s simplicity will make your code more maintainable and easier to debug.
If your project grows significantly or you need advanced features like change tracking or lazy loading, you can always migrate to EF Core later. For now, Dapper should provide all the object mapping capabilities you need without the extra baggage.
dapper’s probs ur best bet here. its quick n easy for small projects like urs. EF Core’s cool but might be overkill. stick with dapper if ur comfy with SQL, it’ll make things smoother. plus, u can always switch later if ya need fancier stuff. just my 2 cents!