Generic CRUD operation

Question

User-1889312591 posted

Hello,

Is there any way or design pattern can I use to get Generic CRUD operation?

Because   I’m working on n-tire application using EF in the data layer and I don’t want to use CRUD Functions in Every Entities.

Your help would be appreciated

Answer 1

User653228039 posted

Look into MVC for ASP.NET.  It has a lot of built-in features to create pages for each of the CRUD operations.

Check out this tutorial to implement a semi-complex application using MVC:

http://nerddinnerbook.s3.amazonaws.com/Intro.htm

Answer 2

User-1889312591 posted

Thanks for your response, but I'm not using MVC I use the asp.net WebFrom.

So Is there another solution??

Answer 3

User1491356988 posted

Check out Linq to SQL or Entity Framework or any other ORM tool. 

Answer 4

User-1889312591 posted

I heard about the Repository Pattern .Is that the right technical to use with EF to get the Generic operation in n-tire application?

Answer 5

User-1636183269 posted

I will prefer to use Entity spaces. 

Answer 6

User-1889312591 posted

Sorry,

Can you give more details? 

Answer 7

User-1636183269 posted

Video: http://developer.entityspaces.net/videos/ES2009_preview/ES2009_StarterApp.html

 http://www.entityspaces.net/portal/TrialDownload/tabid/177/Default.aspx

http://www.brothersoft.com/entityspaces-.net-architecture-51620.html

It is chargeable but easy for rapid development.

Answer 8

User-1889312591 posted

Thank you for you response

but Is there any problem in Repository Pattern or Unit Of Work Pattern ????

Answer 9

User653228039 posted

I use repository pattern for Linq To Sql.  The Nerd Dinner tutorial I listed above actually discusses how to do it.  I haven't worked with the Entity Framework much, so I'm not sure how easy it is to port over, but I imagine the concepts are the same.  I like the repository pattern because you can swap out your underlying datamodel framework and the rest of your code can remain unchanged.  So if your code does something like this:

UserAccount userAccount = userAccountRepository.GetUser(userId);

and you decide your datamodel has to change significantly for whatever reason, all your business logic can stay the same if you just modify the "GetUser" function.