What is the benefit of creating WCF and UI in different solutions?

Question

1.00/5 (1 vote)

See more:

, +

Hi, In my organisation i found that they create 2 solutions,

First will contain WCF, DAL and Business Logic Layer.
Second solution will contain only UI.

In second solution we give reference of DLL's of first solution.

Now, my question is that, why can't we keep all WCF, DAL, BLL, UI in single solution.

I want to know the benfits attached with keeping multiple solutions.

Posted 8-Jun-15 20:39pm

ShamsuddinMalbari

Updated 8-Jun-15 21:24pm

Add a Solution

Comments

Sergey Alexandrovich Kryukov 9-Jun-15 4:20am

The whole idea of thinking of "benefits" is a wrong way of thinking. This is the same as asking "what are the benefits of having a nose?" :-)
—SA

ShamsuddinMalbari 9-Jun-15 4:46am

This question is in context of architectural benefits, it is not limited to technical benefits. There could be some difference in both approachs.

Sergey Alexandrovich Kryukov 9-Jun-15 10:22am

No matter what kind of benefits, still makes no sense. You can talk of benefits only if there are alternatives...
—SA

3 solutions

Solution 2

Are you saying that there are 2 solutions hosted?
1 -> WCF, business Layer
2 -> UI

If yes, May be all the UI related stuff will run in 2nd solution worker process.
And from these UI, You are calling WCF service for the business actions to be taken place, This will be carried out by 1st solution worker process.

May be for reducing load they are keeping this separation.

Posted 9-Jun-15 1:53am

Nibin22

Solution 3

The only benefit I can think of is that the UI be using WPF then there may be some sort of 'creative' department writing the UI solution separately to the development team writing the business logic. Would be pretty unusual though I'd think. I'd have everything in one solution but separate projects.

Posted 9-Jun-15 2:04am

Wastedtalent

Add a Solution

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

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-06-08T22:18:00

Who told you that it should be separate solutions?! Solution should always be one, but the projects should be different, put in the same solution. I don't think anyone needs explanation why the project should be different, but basically: because one project produces one assemblies, and some assemblies certainly should be different.

First of all, "will contain WCF, DAL and Business Logic Layer". An application cannot "contain WCF", which is Windows Communication Foundation, not the part of your project. If "WCF" really means WFC-based Windows Service, or ASP.NET based service, such service certainly should be isolated from UI (how else? a service cannot have UI!) That means UI should be in a separate layer. And so on…

—SA

What is the benefit of creating WCF and UI in different solutions?

3 solutions

Solution 2

Solution 3

Solution 1

Add your solution here

Preview 0

What is the benefit of creating WCF and UI in different solutions?

3 solutions

Solution 2

Solution 3

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us