Multi tier ASP.NET C# web application ditribution

Question

1.00/5 (2 votes)

See more:

Hi,

I'm designing a distributed system. usually I put different parts of the entire project inside different project. here I have a question is it a good thing that I divide each single project in two different projects like I put interfaces in one project and put the other classes inside another project?

What I have tried:

Well I've done it in both way. I wanna know which one is better.

Posted 22-Apr-16 5:59am

m.r.m.40

Updated 22-Apr-16 8:17am

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)

Jason Henderson · Answer 1 · 2016-04-22T08:17:00

Solution 1

It depends. If you are using WCF, then you could install the interface libraries on the client and leave the implementation libraries on your server.

Posted 22-Apr-16 8:17am

Jason Henderson

Comments

m.r.m.40 22-May-16 8:49am

It's a good Idea, Thanks.