I don't think you need to add any ORM layer in Repository pattern, after reading your question details, looks like you are already using Entity framework but Code first approach. ADO.NET is used to map your database table into your project using Database first approach.

So, if you want to add ADO.NET ORM in Repository pattern , here is the link which may help

Yes, currently i am using EF. But my question on my mind is what if I switch to EF to ADO.Net.

They say repository pattern helps you to abstract and able to switch orm later. I just want to test it out if my repository pattern is correct by switching EF to ADO.Net or Dapper or Nhibernate and etc with
sample code and implementation without affecting the EntityFramework
to enable me to switch back and forth to different orms/databases.

I am thinking (dont know if i am right but i believe not) to create another implementation for ADO.NET of the repositories because
the only one will still the same is the repository interfaces . They
(referirng to ado.net and ef) both inheriting to the same repositories but different implementation. I am thinking was AdoNETContext and EFContext. So my
Controller will not be touched only the Injection and DAL if ever.

0

At:- 6/28/2018 10:17:57 AM
Updated at:- 6/28/2018 10:25:32 AM

When you switch from EF Code first to ADO.NET database first, you need to do same Code changes like you do without Repository pattern, benefit of using repository will be you just need to change code in only one level where are you are accessing database, other projects in your solution remain's same.
0