How to separate DAL and BLL when data access is happening through importing dlls?

Question

0.00/5 (No votes)

See more:

I have a service layer project in which all the data access and business logic is inside web methods. I want to to refactor the code such that all the concerns are separated. The data access is happening by using methods from imported dlls(Does not have any link to our own database. We are using some third party dlls). How can refactoring be done in this situation? What would be the best design for this case?

What I have tried:

Searched but could not find appropriate solution.

Posted 28-Mar-16 0:26am

Krati Garg

Updated 31-May-16 1:52am

Add a Solution

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)

prashantmuli · Answer 1 · 2016-05-31T01:52:00

Solution 1

Refer all that Data access dll in DAL Layer. Access DAL in BL layer. and BL in your Page behind.
DAL - Separate Library project.
BL - Separate Library Project.
Application.> BL > DAL.

Posted 31-May-16 1:52am

prashantmuli