在不同的解决方案中创建WCF和UI有什么好处? [英] What is the benefit of creating WCF and UI in different solutions?

查看:95
本文介绍了在不同的解决方案中创建WCF和UI有什么好处?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的组织中,我发现他们创建了2个解决方案,



首先包含WCF,DAL和业务逻辑层。

第二个解决方案只包含UI。



在第二个解决方案中,我们提供了第一个解决方案的DLL的参考。



现在,我的问题是,为什么我们不能将所有WCF,DAL,BLL,UI保存在单一解决方案中。



我想知道附带的benfits保持多种解决方案。

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.

推荐答案

您是说托管了2种解决方案吗?

1 - > WCF,业务层

2 - >用户界面



如果是,可能所有与UI相关的内容都将在第二个解决方案工作进程中运行。

从这些UI中,你是为将要进行的业务操作调用WCF服务,这将由第一个解决方案工作进程执行。



可能是为了减少负载,他们保持这种分离。
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.


我能想到的唯一好处是UI正在使用WPF,那么可能会有某种创意部门将UI解决方案单独编写到编写业务逻辑的开发团队。虽然我想,这将是非常不寻常的。我在一个解决方案中有所有内容但是单独的项目。
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.


谁告诉你它应该是单独的解决方案?!解决方案应该始终是一个,但项目应该是不同的,放在同一个解决方案中。我认为没有人需要解释为什么项目应该是不同的,但基本上是:因为一个项目产生一个组件,一些组件肯定应该是不同的。



First总之,将包含WCF,DAL和业务逻辑层。应用程序不能包含WCF,即Windows Communication Foundation,而不是项目的一部分。如果WCF真的意味着基于WFC的Windows服务或基于ASP.NET的服务,那么这种服务肯定应该与UI隔离(如何服务?服务不能拥有UI!)这意味着UI应该位于单独的层中。等等...



-SA
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


这篇关于在不同的解决方案中创建WCF和UI有什么好处?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆