How to use Interfaces in my asp.net webapplication by using 3 tier architecture and entityframwork.

Question

1.00/5 (1 vote)

See more:

, +

I would like to use interfaces in my asp.net webapplication by using Entityframwork and 3 tier architecture could u please suggest me how to maintain interfaces and which type of method i have to maintain interfaces?

Is it better approach that maintaining interfaces in application?

Posted 9-Jan-14 22:30pm

DGKumar

Add a Solution

Comments

Jameel VM 10-Jan-14 4:45am

What is the problem you are facing? what you are trying to achieve?

DGKumar 10-Jan-14 5:39am

Hi could you please provide the some links for this approach i tried but i could not get better approach for this

mopicus 10-Jan-14 7:46am

Here in CodeProject there is an explanation on Domain Driven Design approach
http://www.codeproject.com/Articles/56767/Domain-Driven-Design

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

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.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

mopicus · Answer 1 · 2014-01-09T22:51:00

Kumar, I usually follow this approach :

Place domain classes and interfaces that the business logic must implement in an assembly, called Domain. This includes I[]Service and I[]Repository interfaces. The domain does not have any references to any other project. For example ICustomer, ICustomerRepository, ICustomerService.

On another assembly I put all the DB logic, and implement the IRepository interfaces, ICustomerRepository.

On another assembly I put all the Service logic, and implement the IService interfaces. ICustomerService. Services are the bridge between the db layer and the front end layer, which can be ASP.Net or MVC

I've found this approach in having layers very independent, and a code more maintenable.
Hope this helps!