Home/ Questions/Q 7783127
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T19:45:01+00:00

Need suggestion for migration few modules of asp.net mvc 3 application: Right now we

  • 0

Need suggestion for migration few modules of asp.net mvc 3 application:
Right now we are using EF with POCO classes, but in the future for some performance driven modules we need to move to ADO.NET or some other ORM tool (may be DAPPER.NET).

The issue we are facing as of now is: our views dependent on Collection classes getting loaded through EF, what strategy should i used for these entity classes to be get loaded exactly the same way as by EF with some other ADO.NET or ORM tool.

What i want is to be able to switch between EF & ADO.NET with minimum of change at data access layer, as i don’t want my Views to get effect by that.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should use the Repository Design Pattern to hide the implementation of your data access layer. The Repository will return the same POCO’s and have the same operations contracts no matter what data access layer you are using underneath the hood. Now this works fine if you are using real POCO’s that do not have virtual methods for lazy loading in them. You will need to explicitly handle loading of dependent collections on entities to make this work.

    • 0