How do I deploy and configure distributed app   

I have developed a test three-tiered application to demonstrate to dev team.  
I have a UI Layer, a Business Logic Layer, a Data Access Layer connecting to 
s SQL server layer.  
My solution comprises the following assemblies
Test_WIN (Test_WIN.exe - Windows UI)
Test_WEB (Web UI)
Test_BLL (Test_BLL.dll - Business Logic Layer)
Test_DAL (Test_DAL.dll - Data Access Layer)

The UI (both Windows & Web) are thin clients that reference Test_BLL.dll
Test_BLL.dll passes data to Test_DAL.dll (and Test_DAL.dll passes data back 
to Test_BLL.dll)
Test_DAL.dll executes stored procedures on SQL Server database

All of this works perfectly well when Test_WEB, Test_WIN.exe, Test_BLL.dll & 
Test_DAL are all on same physical machine.  What Im not sure how to do is 
demonstrate is how to get my app working if I deploy my logical layers onto 
different physical machines ie I want Test_WEB on my web server and my 
Test_BLL & Test_DAL on a different machine.

Could someone either describe how (or point me to a resource) I set up and 
configure this scenario.  What Im looking for is a step by step guide to 
deploy the different components that I have developed

Any help appreciated

date: Wed, 23 Jul 2008 14:29:01 -0700   author:   Terry Holland am

Re: How do I deploy and configure distributed app   

Hi Terry,

With .NET you can't just deploy your dll's as distributed components. 
You need to put them into some kind of distribution mechanism, in the 
past there has been several to choose from including:

- ASP.NET Web Services, a SOAP based technology hosted inside ASP.NET
   http://msdn.microsoft.com/en-us/library/ms972326.aspx

- Remoting, a native .NET remote objects technology that can be hosted
by ASP.NET or in your own host. 
http://www.devarticles.com/c/a/C-Sharp/An-Introduction-To-.NET-Remoting/

- COM+ and DCOM, this was initially here for backwards compatibility and 
is not something I recommend.
  http://msdn.microsoft.com/en-us/library/ms973484.aspx

The prefered solution today, and what I recommend, is to use Windows 
Communication Foundation as the hosting mechanism for distributed 
applications, which you can read more about here:

http://msdn.microsoft.com/en-us/library/aa480190.aspx

I hope this helps.

-- 
Patrik Löwendahl
http://www.lowendahl.net
[MVP] [MCT - Enterprise Application Development]

Terry Holland skrev:
> I have developed a test three-tiered application to demonstrate to dev team.  
> I have a UI Layer, a Business Logic Layer, a Data Access Layer connecting to 
> s SQL server layer.  
> My solution comprises the following assemblies
> Test_WIN (Test_WIN.exe - Windows UI)
> Test_WEB (Web UI)
> Test_BLL (Test_BLL.dll - Business Logic Layer)
> Test_DAL (Test_DAL.dll - Data Access Layer)
> 
> The UI (both Windows & Web) are thin clients that reference Test_BLL.dll
> Test_BLL.dll passes data to Test_DAL.dll (and Test_DAL.dll passes data back 
> to Test_BLL.dll)
> Test_DAL.dll executes stored procedures on SQL Server database
> 
> All of this works perfectly well when Test_WEB, Test_WIN.exe, Test_BLL.dll & 
> Test_DAL are all on same physical machine.  What Im not sure how to do is 
> demonstrate is how to get my app working if I deploy my logical layers onto 
> different physical machines ie I want Test_WEB on my web server and my 
> Test_BLL & Test_DAL on a different machine.
> 
> Could someone either describe how (or point me to a resource) I set up and 
> configure this scenario.  What Im looking for is a step by step guide to 
> deploy the different components that I have developed
> 
> Any help appreciated
> 
>

date: Fri, 17 Oct 2008 12:55:52 +0200   author:   Patrik Löwendahl [MVP]