We also talked about this tab being “Configuration” aware, which means that you can set different properties per build environment like Debug, Testing, Staging, Release/Production etc and all of these properties will be saved in your project file. In the previous post we talked about “Creating a Web Package using VS 2010” where we discussed setting up the Package properties in “Package Tab” of the project’s property pages as shown below:Īll the properties that you set up in this UI are stored in your. In anycase, the entire Web Deployment story in VS 2010 uses MSBuild behind the scene which means that all the UI features in Visual Studio are actually wrappers over the underlying MSBuild Targets, Tasks and Properties. You can certainly take your build automation process to its best by using Continuous Integration model which we will discuss in subsequent posts. 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…Īnyways, if you choose to automate your build process there are various tools and technologies available out there, some of the popular ones are: In this post I will cover web package creation using MSBuild command line. Web Packaging: Creating a Web Package using VS 2010.

I would recommend reading the the preceding posts to get an overview of all the scenarios supported: 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.

Creating a zip file in microsoft 2010