Shulou(Shulou.com)06/02 Report--

This article introduces the knowledge of "what is ADO.NET Entity framework". In the operation of actual cases, many people will encounter such a dilemma. Then let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

I used to hear that Enterprise Library abstracts a higher-level class library from the point of view of enterprise applications on the basis of net framework library, for example, involving the data access layer. Later, in the process of learning, I encountered difficulties when trying to build entity classes in an object-oriented way. After learning, I originally needed o/rm framework to solve the problem.

As a result, Linq to sql and ADO.NET Entity framework were discovered. However, too many frameworks have confused their own direction. Excuse me, what is the relationship between these frameworks, or is it irrelevant at all? Does Enterprise Library use Linq to sql or ADO.NET Entity framework when accessing related classes?

Or Enterprise Library basically still uses the old data access technology of ado.net, the data access layer of implementation such as sqlcommand dataadapter. Oh, by the way, my main concern is the technology of the data access layer part of the three-tier architecture. What I want to learn about the business logic layer is the kind that is implemented through entity classes, not a lot of datatable.

ADO.NET Entity framework: equivalent to NHibernate, it is a full-featured ORM officially developed by Microsoft for a long time.

Linq to sql: it is a simplified version of ORM, which is more convenient. It has no caching function of normal ORM, practical inheritance function, and mapping is also very inconvenient. But because of the integration of Linq, it is very convenient. My personal view is that Microsoft has come up with a deceitful trick in the case that ADO.NET Entity framework has been unable to come up with for a long time. Small projects can be used, but complex large projects will kill people.

Enterprise Library: is a helper class library, including not only data access encapsulation, but also AOP and so on. My view is, like lazy woman's foot-binding, smelly and long, do not use it, have time to learn it, it is better to use Linq to sql; to use Linq to sql, it is better to wait for the official version of ADO.NET Entity framework; rather than wait for the official version of ADO.NET Entity framework, it is better to encapsulate a database access layer, not only freely control the code, but also spend less time, but also learn the way to look at the problem from the perspective of the class library.

That's all for "what ADO.NET Entity framework is". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.