-4

I am creating a web portal on real estate. I am building it on ASP.NET MVC 5. For database connectivity, should I use Entity framework or not? and why? If not then what should I use? (I was using normal sqlclient method when I was working on web forms).

Updating for more clarity : I am having very complex query scenarios in my project such as I have to search n various filters etc. I am also using angular ajax for many features. Now can anyone suggest either go with EF or not?? Thanks

Shahbaz Khan
  • 133
  • 1
  • 10

2 Answers2

0

There are several infrastructures designed to help you create websites using ASP.NET. The EntityFramework, which is part of ADO.NET, help you do ORM, MVC 5 is, well, for MVC. There are others, like Razor.

All in all, it seems fine to use EF for DB connectivity and ORM, as it seems to be the standard.

Itai Bar-Haim
  • 1,686
  • 16
  • 40
0

Use an ORM (like Entity Framework) because it will read data from a database and give you back some easy to use classes, manage change tracking, allow easy updates, etc, etc. These two articles may help as they list of ORMs and contain some performance data:

Fetch performance of various .NET ORM / Data-access frameworks

Fetch performance of various .NET ORM / Data-access frameworks, part 2

Also you may want to take a look at this Stackoverflow question:

Are there good reasons not to use an ORM?

Community
  • 1
  • 1
MotoSV
  • 2,348
  • 17
  • 27