Browse by Tags
All Tags »
PM (
RSS)
Today I just saw a question posted on stackoverflow.com asking Why are some Web.config transforms tokenised into SetParameters.xml and others are not ? Let me give some background on this topic for those who are not aware of what the question is. With Visual Studio 2010 when you package your application using the Build Deployment Package context menu option, see image below. When build the package by default the package will be created in obj\{Configuration}\Package\{ProjectName}.zip where {Configuration} is the current build configuration, and {ProjectName} is the name of the project. So in this case I since I’m building with Debug and the project name is MvcApplication1 the package will be placed at obj\Debug\Package\MvcApplication1...
Today I want to advance our discussions around Web Deployment in Visual Studio 10… To catch up on the previous discussions in this series check out: Web Deployment with VS 2010 and IIS Web Packaging: Creating a Web Package using VS 2010 Web Packaging: Creating web packages using MSBuild How does Web Deployment with VS 10 & MSDeploy Work? In this post I will focus on installing the MSDeploy based Web Packages to IIS. You can actually install/deploy web packages using multiple different avenues listed below: Using IIS Manager UI Using command file created by Visual Studio 10 Using command line using MSDeploy.exe Using Power Shell support provided by MS Deploy Using managed APIs provided by MS Deploy VS 10 will create Web...
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...
In the earlier post I highlighted various investments that we are making in Visual Studio 2010 and IIS to make Web Deployment easier. You can read that post below: Web Deployment with VS 2010 and IIS Deploying a web project with all its correct dependencies is not a trivial task. Some of the assets which need to be considered during deployment are: Web Content (.aspx, .ascx, images, xml files, PDBs, Binaries etc) IIS Settings (Directory browsing, Error pages, Default Documents etc) Databases that the web project uses GAC Assemblies and COM components which the web project depends upon Registry Settings that may be used within the web project Security Certificates App Pools In an enterprise environment a web application with all of its...
Today, deploying a web application is not as easy as it should be. Whether you are deploying your web to a shared hosting environment and paying monthly to maintain it OR whether you have a web server/s managed by your enterprise, there are a lot of manual steps involved in getting your application from point A to point B. If you are deploying your web application to a shared hoster then today you have to use technologies like FTP which take a long time to get your web content to the hosted server. After deploying your content you have to manually go to hoster control panel and install your database by running sql scripts and configure various IIS settings like marking a folder as an application to isolate it from the rest of the application...
Web Deployment Projects (WDP) allows you to pre-compile your web into binaries and further also allows you to merge the assemblies produced in the format that you like. In my earlier posts I had talked about various WDP features and the latest release of WDP for VS 2008. You can read more about this here By default in the WDP output you will find project files (.csproj/.vbproj), user files (.user), .PDB, obj folders and other artifacts which are not required for web to run. It is pretty easy to get rid of these files automatically by following these simple steps: Step 1 - Open WDP project file for editing Open WDP project file by right clicking on the WDP project and clicking "Open Project File" Step 2 - Exclude Read...
The Visual Web Developer team is looking for a few talented and experienced invididuals to join our team. We have opportunities in development, testing, and program management. Our team builds Visual Studio features that enable creating applications for ASP.NET, IIS, Silverlight and Sharepoint. Here are links to our current openings: Program Manager Lead Software Development Engineer Lead Software Development Engineer in Test To submit your interest in any of these positions, please email -- venusblg-at-microsoft-dot-com -- with an attached resume. -- Visual Web Developer Team Read More...
First a quick intro, since this my first post on the team blog. My name is Omar Khan. I'm the group program manager for the web development tools team. I manage the program management team that helps design the web tools inside of Visual Studio. This post is one of a three part series that describes how to factor development of a single large ASP.NET application into multiple projects inside of Visual Studio 2005 using the Web Application Projects add-in. Part 1 of 3: In this post, I’ll describe the basics on how to setup a sub-project structure using IIS. Part 2 of 3: The next post will describe intricacies with master pages, user controls, and project references when using a sub-project structure. Part 3 of 3: The final part to the series...
More Posts