-3

I’m trying to learn to develop using asp.net mvc. but yea, using the EF style is quite different than what I’m used to and that is the ADO. What I wanna know is, should I really use the EF approach, or could I still use the ADO approach. I just wanna know what’s better.

Konamiman
  • 49,681
  • 17
  • 108
  • 138
delbertwah
  • 15
  • 3
  • http://stackoverflow.com/questions/22328889/entityframework-vs-pure-ado-net – Alex Nov 11 '15 at 12:36
  • http://stackoverflow.com/questions/2698151/entity-framework-vs-linq-to-sql-vs-ado-net-with-stored-procedures – Alex Nov 11 '15 at 12:37
  • http://stackoverflow.com/questions/27270124/entity-framework-vs-ado-net – Alex Nov 11 '15 at 12:37
  • *"I just wanna know what's better"* = opinion based response = off-topic for SO. Both have their advantages or you could use another ORM such as nHibernate. *"Can you use ADO"* (as per question title) - obviously otherwise you wouldn't be asking which is better. – freedomn-m Nov 11 '15 at 13:58

1 Answers1

2

I just wanna know what’s better

Depends on your definition of "better".

Inform yourself about Entity Framework, about its strong and weak points (especially the weak points!), experiment with it, and if you feel that it will really help you to save time and produce good quality code, then by any means use it. If not, there's absolutely nothing wrong with using plain old ADO.NET (altough using a tool like Dapper certainly helps in this case).

Konamiman
  • 49,681
  • 17
  • 108
  • 138