3 ms·
This makes me feel a bit better about sticking with ol' ADO.Net.
by artmageddon 9y ago
This makes me feel a bit better about sticking with ol' ADO.Net.
- deleted 9y ago[deleted]
- sklarsa 9y agoDepending on your use case, that can have disadvantages too. For example, I imagine it would be quite difficult to refactor your code around any database schema changes if you're writing raw SQL queries in ADO. Many modern ORMs, including Entity Framework, have a "code-first" approach, allowing you to modify your mapped objects in code and then programatically perform the related schema changes in the database. In a compiled language like C#, this makes refactoring fairly painless. Also, ORMs do reduce a lot of boilerplate code needed to perform CRUD operations, reducing the potential of introducing new errors into your data access layer. While I understand that ORMs are not for everyone, and certainly have their limitations, I think that in this day in age, they're at least worth investigating. Even in the .NET space, there are other ORM options to choose from aside from Entity Framework.
- artmageddon 9y agoI'll have to admit the lack of ability to do quick refactoring has bitten me on more than one occasion.. :/
- zip1234 9y agoDepending on which version of EF you are using, it is just a wrapper around ADO.Net