views:

171

answers:

1

I want to automate publishing a VS2005 ASP.NET Web Application Project to a disk path from the command line as part of my build process (i.e. the equivalent of selecting Build/Publish from the IDE).

I've tried Microsoft's Web Deployment Project, and it seems half-baked to me: it deploys files that are not part of the Web Application project, for example csproj, csproj.user, files used by my source control provider, etc...

Googling suggests explicitly excluding certain file types from the Web Deployment project, but I really want "opt-in" (i.e. only deploy files that are in the project) rather than "opt-out" (deploy everything except what is explicitly excluded).

I'm happy to have a copy of VS2005 on my build server (I need it to build Setup projects anyway).

What's the best way to achieve this? Can this be automated from the command line?

A: 

Does the following help you...

http://stackoverflow.com/questions/674501/publish-a-website-using-msbuild

Martin Peck
No, that exxplains how to publish a website. It doesn't address the problem that Web Deployment Projects deploy unwanted files.
Joe