All geek questions in one place

So many data access options, what to use?

I am an asp.net web application developer and I have always used the DABA Enterprise Library with stored procedures to access data with 4 separate layers (presentation layer, user type layer, business logic level and data access level).

I feel this approach is time consuming.

I have not worked with other ways to access data, but I am sure that there are many ways to save development time. During the search, I read about this:

  • Data adapters generate entire DALs with stored procedures.
  • Linq with various flyers
  • Entity Framework
  • Using data controls such as SQLDataSource and Dynamic Data li>
  • Other Converters, Code Generators, and Utilities

With so many options and my little knowledge, I am confused in deciding which development step I should take, given that my development can be fast, expandable, reusable and standard. I also want to find a way in which my code libraries can be used with other technologists, such as silverlight, mvc framework, services, if I ever need.

Please help me and help.

thank

+3
source share
3 answers

, SQL Server, (ORM) . .NET Entity Framework Microsoft NHibernate . .

Entity Framework drag-n-drop Visual Studio NHibernate . , .

, CRUD, , , , , .

+4

- . , , , , . , , . , .

+3

(Adapter, Repository, MVP ..). , . , , - . , , , , . .

You can also look at the MVC # framework or the ASP.NET MVC framework from Microsoft. Regarding the repository template, did you consider NHibernate ?

Good luck.

+2
source

Source: https://habr.com/ru/post/1760985/

More articles:


All Articles