Configuration and Deployment

Re: Web app Deployment

dotnetsamurai — Mon, 26 Feb 2007 13:13:59 GMT

You should understand that the "Web Setup" project and "Web deployment" projects are two different things.

The web setup project is for creating an msi that installs the web application.

The web deployment project is for creating a ready-to-deploy version of the web site. The output of the web deployment project can have the source removed (non-updatable), which is useful for hiding intellectual property. Also, it is precompiled, which avoids compilation when the web app is running.

Re: Web app Deployment

Claude Maxim — Wed, 06 Dec 2006 17:21:27 GMT

Hi doUMissClassic,

Once you publish to a local folder, do you just ftp it all to the host? And if so, how is the database handled?

Thanks,

Claude.

Re: Web app Deployment

chrisbarber1 — Wed, 06 Dec 2006 07:06:12 GMT

Great! Thanks for the advice!

Re: Web app Deployment

doUMissClassic — Tue, 05 Dec 2006 21:41:38 GMT

You wouldn't want the source files on your server because even though they are unaccessible to the client, anyone who has access to the server could view them.

The easiest way to deploy if you're using 2005 is to R-Click on project and do Publish Web Site to a local folder.

This makes a creates a compiles version of the site (.cs -> .dll's). You are left with just the minimum pages you need to run the site, and no source :)

Re: Web app Deployment

pkellner — Tue, 05 Dec 2006 17:23:19 GMT

Rick Strahl's got a good one in code magazine.

http://west-wind.com/weblog/posts/5601.aspx

Re: Web app Deployment

chrisbarber1 — Tue, 05 Dec 2006 16:28:13 GMT

Does anyone know of any good articles about this where I can read up?

Re: Web app Deployment

chrisbarber1 — Tue, 05 Dec 2006 09:37:31 GMT

But wouldnt this mean that there would be a whole lot of .resx, .vb, .cs files rolling around in the directory unnecessarily?

Is there any risk of leaving any business logic open to interference?

Re: Web app Deployment

pkellner — Sat, 02 Dec 2006 22:15:06 GMT

You do not need to setup a web deployment project. I usually just copy as you suggest. the web deployment projects are for things like building dll's and other types of deployments you may not need.

Web app Deployment

chrisbarber1 — Sat, 02 Dec 2006 21:57:29 GMT

Hi,

A very basic question that I am struggling to understand.

When deploying a asp.net web application why should I create a web setup project? Why can't I just copy, by ftp, the source files to the destination webserver?

Many thanks