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?
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.
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 :)
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.
[This post is not provide AS IS, has warranties, and confers rights]
chrisbarber1
Member
115 Points
24 Posts
Web app Deployment
Dec 02, 2006 08:57 PM|LINK
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
asp.net 2.0
pkellner
All-Star
24018 Points
3616 Posts
ASPInsiders
Moderator
MVP
Re: Web app Deployment
Dec 02, 2006 09:15 PM|LINK
http://peterkellner.net
Microsoft MVP • ASPInsider
chrisbarber1
Member
115 Points
24 Posts
Re: Web app Deployment
Dec 05, 2006 08:37 AM|LINK
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?
chrisbarber1
Member
115 Points
24 Posts
Re: Web app Deployment
Dec 05, 2006 03:28 PM|LINK
pkellner
All-Star
24018 Points
3616 Posts
ASPInsiders
Moderator
MVP
Re: Web app Deployment
Dec 05, 2006 04:23 PM|LINK
Rick Strahl's got a good one in code magazine.
http://west-wind.com/weblog/posts/5601.aspx
http://peterkellner.net
Microsoft MVP • ASPInsider
doUMissClassic
Member
10 Points
2 Posts
Re: Web app Deployment
Dec 05, 2006 08:41 PM|LINK
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 :).
.
webtopus development
ctrl-D blog
chrisbarber1
Member
115 Points
24 Posts
Re: Web app Deployment
Dec 06, 2006 06:06 AM|LINK
Claude Maxim
Member
157 Points
61 Posts
Re: Web app Deployment
Dec 06, 2006 04:21 PM|LINK
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.
dotnetsamurai
Member
143 Points
48 Posts
Re: Web app Deployment
Feb 26, 2007 12:13 PM|LINK
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.