Latest Microsoft Blogs

  The IIS Web Deployment Tool (Web Deploy) and the deployment features introduced in Visual Studio 2010 enable you to automate many deployment tasks, but we have heard you all that many common scenarios not yet documented fully. We are addressing this need by creating step-by-step walkthroughs that will guide you from beginning to end through scenarios that address common real-world needs. Interestingly, this blog post is not the documentation of the solution but actual documentation of problem statements. This post presents the first set of scenarios that we have identified and solicit your feedback to help us determine they are representative enough or not.  If you have any feedback as usual you can post them here as comments or...

Recently I was having a conversation with one of Web Deploy (MSDeploy) users and an interesting scenario came up.  He essentially wanted to move his site from IIS 6.0 to IIS 7 and wanted to consider Web Deploy to do this.  In addition he actually was fine with just xCopy-ing the site’s content from IIS6 server to IIS7 server as it was almost 6GB+ in size and trying to create a zip package for it was not most the optimal way of using resources, nevertheless creating a zip package using Web Deploy for just the IIS configuration is what was certainly desirable due to ease of portability & use. I thought this would be a good opportunity to write a quick note to share with you that migration from IIS 6 to IIS 7 was one of the original...

  Our team recently released WDP for VS 2010… The key features to note for WDP for VS 2010 are: All the core features of WDP 2008 Migration from WDP 2008 to WDP 201o Multi-Targeting support in WDP 2010 Support Web Deploy Packages in the WDP project.. You can read more about the above features on our team blog at Visual Web Developer Team Blog Download WDP 2010 Beta by clicking here!! The guidance around using WDP 2010 is Use it if you want to migrate to VS 2010 and are currently using WDP for VS 2008 Use it for TeamBuild/MSBuild based deployment of Web Site Projects in VS 2010… Use them for Web Application Projects (WAPs) if you feel it is extremely important for you to pre-compile/merge your projects… If not then you can use Web Deployment...

In this post I am hoping to explain how you can change your web.config settings per different server environment using Web Deployment Projects (WDP) for VS 2005 or VS 2008… First of all let me start with the fact that WDP for VS 2005 as well as WDP for VS 2008 are build configuration aware… In fact, special effort was made in WDP 2005 & WDP 2008 to allow configuration specific settings… That is the reason when you look at the WDP UI you can see configuration specific dropdowns as shown below: You can create one build configuration per your server environment eg. “Testing”, “Staging” , “Production” etc and configure all of your WDP settings per build configuration pretty easily… Learn more how to manage configurations per build environment...

Few days back I summarized the difference between a project system and a project templates ; today I want to focus on key differences between different project systems available for web developers in Visual Studio… You might be aware of the fact that we have two different types of project systems for Web developers i.e Web Application Projects (WAPs) and Web Site Projects (WSPs)…  Often time I get asked this question on which type of project should to use for web development…  Sometimes web developers even start a religious war on the two choices, honestly here you have an option to choose the god of your own choice and this post is my attempt to help you make an informed decision… Most of the time I land up asking questions to people...