How to move ASP.NET app from one machine to two machines.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a simple way to take an ASP.NET application that is currently
working/running on one development machine (designed with UI, Business, and
Data layers) and move it to two machines (one web server in a DMZ and one
application server behind the firewall)?

Do I have to re-write portions of my application to do this?

Your help would be much appreciated.
 
Hi David.

Two things right up front.

1) You posted to ADO.NET. You would find a quicker answer in ASP.NET.
They're close and I have made the same mistake myself on occasion

2) Your question doesn't really give a lot of information in terms of what
your different layers consist of. Your UI layer is not a problem as all you
have to do is deploy the dll files and aspx pages for the site to another
server.

If your business layer contains components that you want on another server,
then you will need to look at how to call the methods in those components.
One likely choice would be to change your access to these business
components into web services and have the web services and the business
components reside on the same machine.

For the data layer, if your database server is seperate from the business
layer server, then you can still use the same access mechanism, you just
need to change your connection string. A good way to handle this is to
place your connection string information in the web.config file and then
access that from within your code. Whenever you change the server you want
to deploy the database on, you just need to modify the web.config file
instead of having to change code and recompile.

Hope that helps.

Gerry O'Brien
Visual Basic.NET MVP
 
How much work - It really depends on your system architecture.

If you have neat layers, then you might want to decide what portions of the
application you wish to segregate and how. Where you want Webservices, where
you want remoting or Where you want MSMQ?

Then you've got the issue of SAO vs.CAO - where would you want to choose
which and why.

Then you've got the issue of chunky vs. chatty - How much data is good to
read in one shot and what should be left to a lazy load.

... in short .. this requires a discussion and a fantastic explanation of
your current architecture, but the above points must be considered. A book
I'd recommend is Advanced Remoting (Apress) by Ingo Rammer.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
 
Gerry (and Sahil), thank you for your replies.

I’m going to focus on Remoting with Web Services as a backup plan. Our
application implements a strong object model and “should†lend itself well to
Remoting.

If I get stuck I’ll be posting additional questions. Thank you again for
taking the time to share your insights.

-- David
 
Back
Top