blogs.msdn.com — This post is next in the series of VS 2010 articles that we have been putting together to dive into the Web Deployment improvements with VS 2010 and IIS. I would recommend reading the the preceding posts to get an overview of all the scenarios supported: * Web Deployment with VS 2010 and IIS * Web Packaging: Creating a Web Package using VS 2010 In this post I will cover web package creation using MSBuild command line. Many medium to large sized teams plan on automating their build process for various good reasons like predictability for QA team, time saving as compared to on-demand manual build, early bug detection with Build Verification Tests (BVTs), knowing the current state of project integration, etc… Many argue that setting up the build system is not worth the trouble for a small project running only a few months; I would suggest otherwise, believe me setting up an automated build process once will pay you back enough just within a few weeks and will get you into a mode where in the future doing this will be so much more easier… original link