views:

1220

answers:

8

When I build my ASP.NET web application I get a .dll file with the code for the website in it (which is great) but the website also needs all the .aspx files and friends, and these need to be placed in the correct directory structure. How can I get this all in one directory as the result of each build? Trying to pick the right files out of the source directory is a pain.

The end result should be xcopy deployable.

Update: I don't want to have to manually use the Publish command which I'm aware of. I want the full set of files required by the application to be the build output - this means I also get the full set of files in one place from running MSBuild.

+1  A: 

Have you tried right clicking the website in Solution Explorer and clicking 'Publish Website'?

Geoffrey Chetwood
Yes, I can publish the website like that as a manual step, but I want the result of building the solution to place the deployment items in a directory with the rest of the solution build results. This also means a run of msbuild on the build machine gets me what I want.
Simon Steele
If you want an automated build script, you should update your question.
Geoffrey Chetwood
Done, hopefully that's clear enough now.
Simon Steele
+1  A: 

ASP.NET doesn't have real xcopy deployment for new sites. It depends on having a virtual directory/Application in IIS. However, once that virtual directory is created you can use xcopy for updates.

Joel Coehoorn
Right, and I have a powershell script that installs the website providing all the files are present in the right place. When I want to update the website I again need all the files and can xcopy deploy those.
Simon Steele
When you update the site, what is the difference between publishing the site through VS and running your script?
Geoffrey Chetwood
I am developing web sites that are used outside of our corporate intranet - i.e. I need to take the site to a customer and install it there, or have it packaged ready for that. I also want to install an official build of the site from the build server.
Simon Steele
+1  A: 

You can Publish Web site..If you want to automate your deployment, you need to use some script.

Gulzar
A: 

Build --> Publish

A dialog box will appear that will guide you through the process.

Alison
+1  A: 

For the automated building you describe in the update, I would recommend you look into MSBuild and CruiseControl.NET

Geoffrey Chetwood
Hi Rich, I'm using MSBuild already to build the project and this is triggered on every check-in by an internal system a little like CCNet. The problem is that only the assembly from the project is placed in the output directory - no .aspx files or other content - I want the content too.
Simon Steele
+4  A: 

One solution appears to be Web Deployment Projects (WDPs), an add-on for Visual Studio (and msbuild) available that builds a web project to a directory and can optionally merge assemblies and alter the web.config file. The output of building a WDP is all the files necessary to deploy the site in one directory.

More information about Web Deployment Projects:

  1. Announcement on webdevtools MSDN blog for WDP 2008
  2. ScottGu introduction to WDP 2005

The only disadvantage to this solution is the requirement on an add-on which must be available on the build machine. Still, it's good enough for now!

Simon Steele
This is exactly what we use to prepare a release or test copy of the web application/site for users.
icelava
+1  A: 

Have you tried using the aspnet_compiler.exe in your .net framework directory? I'm pretty sure you can create a "deploy ready" version of a web application or web site.

Min
Thanks Min I'll give it a try.
Simon Steele
+1  A: 

The _CopyWebApplication target on MSBuild will do exactly what you need. The catch is that only the main assembly will be copied to the bin folder and that's why a copy task is needed to also copy any other file on the bin folder.

I was trying to post the sample script as part of this post but wasn't able to.

Please take a look at this article on my blog that describes how to create a MSBuild script similar to the one you need.

JCallico