Why use ef4

Submit your solution! When answering a question please: Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem.

Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question. Let's work to help developers, not make them feel stupid. Related Questions. Why ADO. NET instead of entity framework.

Databinding entity framework 6 classes to WPF treeview. Entity framework provider for tibero. Entity framework mysql connection string error? How to save unicode in database using entity framework. Which approach of entity framework should I use in ASP.

Converter SQL to linq C for entity framework. Microsoft has provided a framework called "Entity Framework" to automate all these database related activities for your application. Entity Framework is an open-source ORM framework for. NET applications supported by Microsoft. It enables developers to work with data using objects of domain specific classes without focusing on the underlying database tables and columns where this data is stored.

With the Entity Framework, developers can work at a higher level of abstraction when they deal with data, and can create and maintain data-oriented applications with less code compared with traditional applications.

NET developers to work with a database using. NET objects. It eliminates the need for most of the data-access code that developers usually need to write. Active 8 years, 10 months ago. Viewed 45k times.

If it matters, our client's applications can have anywhere from 10 - 1, active users. Improve this question. Robert Harvey k 54 54 gold badges silver badges bronze badges. Are you using Linq-to-SQL currently? Avoid using SQL directly in your future development. ORM or EF are almost a must. Devote sometime to have a strategy for your data access layer.

It is a critical decision and it is not a trivial task. Make sure you have enough time for you and the team to learn it. Introduction of new core technology to the team must be managed. Choose the tool, choose the material, have some education, New or existing databases? Show 1 more comment. Active Oldest Votes. Much easier to maintain No longer need to remember to parse my input before building an in-line sql statement, which means less chance of a SQL injection attack of course, it's still possible depending on your queries, but much less likely Cons Cannot span multiple databases Or use a Stored Procedure.

I've had issues with some default values defined on SQL server not getting pulled into the entity model after a new record gets added. It's possible you can re-work that query as a SP or View.

This doesn't happen that often though. I've had a few issues with trying to create an association between tables that do not have a Foreign Key defined in SQL Server. Improve this answer. Rachel Rachel EmmadKareem Its an ok restriction if you have control over the database, but if you're working with a 3rd party database, or with views, it can be a bit annoying — Rachel.

Just try using EF in a disconnected N-Tier web app - updating entities in a session and M-M relationships, hmmmmm what fun! EmmadKareem entities really need a single valued primary key - using composite keys is a nightmare in EF. This is a con rather than a reasonable restriction. I'd say security is another issue. Many think all DB access should go through stored procedures with DB roles associated with procs to determine what logins can execute what stored procs.

I've used EF but have come across clients cough Microsoft who had these security requirements — Mick. Show 8 more comments.