Basic Microsoft Web Deployment Tool Setup For Visual Studio 2010

Basic Microsoft Web Deployment Tool Setup For Visual Studio 2010

  • Comments 6

In this blog post I will explain how to get and install the Microsoft Web Deployment Tool, so you can share created packages with others and how to setup a Windows 2008 Server to allow packages to be deployed from Visual Studio 2010 Beta 1. Visual Studio 2010 Beta 1 ships with and installs Microsoft’s Web Deployment Tool as part of the Visual Web Developer. In order to set up a server for publishing or allowing machines to deploy packages created in VS 2010 you will need to download and install the Web Deployment Tool RC1 from the IIS Download Center. Note that newer versions of the Web Deployment Tool may not be compatible with VS 2010 Beta 1. If needed, VS 2010 Beta 1 has the Web Deployment Tool MSIs located in the WCU\MSDeploy directory of the DVD.

Setup for Package Installation:

To consume packages created by Visual Studio Beta 1 or the Web Deployment Tool, you will need to install Microsoft’s Web Deployment Tool. Below are two different options for installing the Web Deployment Tool:

  1. Microsoft Web Platform Installer
    1. Download Microsoft Web Platform Installer 2.0 Beta from link above.
    2. Under the “Web Platform” tab choose “Customize” Web Server and check “Web Deployment Tool 1.0 RC”
    3. Select “Install” 
      WebPI
    4. The “Install” screen will appear with any needed dependencies. Click the “Accept” button.
  2. Install from MSI
    1. Launch the x86 or x64 Web Deployment Tool’s MSI (information for MSI located above.)
    2. Read and accept EULA. Click Next.
    3. Select Typical.
    4. Select Install.

Microsoft Web Deployment should now be installed and useable by the command file generated from VS 2010 for deploying.

Setting up the Web Deployment Tool’s Web Management Service (WMSvc) for administrator publishing on Windows 2008 Server:

Installing the Web Management Service allows users to publish Web Applications from Visual Studio 2010 Beta 1 directly to the server, cutting down on time and steps required to publish applications. Some of the features the Web Deployment Tool helps with are creating applications during deployment and performing incremental publishing. With administrator publishing on IIS 7, users can publish IIS Setting, change the web application’s physical path, and transport Application Pool configurations. 

  1. Make sure the Web Server (IIS) role is added to the Server.
  2. In the Role Service section, make sure that the Security node and under Management Tools the Management Service is installed.
    WebServerRoles
  3. Launch the x86 or x64 Web Deployment Tool’s MSI.
  4. Read and accept  EULA. Click Next.
  5. Select the “Custom” option on the “Choose Setup Type” dialog.
  6. You should now be presented with following options:
    CustomSetupFeatures
  7. Select the “Web Management Service” to install the WMSvc handler used by One-Click Publishing.
    1. “Packaging User Interface” will allow you to install packages created in VS 2010 through Internet Information Services Manager (inetmgr.exe).
    2. “PowerShell Snapin” adds Power Shell functionality.
    3. “Web Management Service” is used by One-Click Publish.
    4. “Remote agent service” is another option for publishing, but is not used by One-Click Publish.
  8. Finish Web Deployment Tool setup.
  9. Go back to the Server Manager window and expand the “Configuration” section.
  10. Under the “Services” node. If present make sure the “Web Deployment Agent Service” and “Web Management Service” are Started and have a Startup type of “Automatic”.
  11. Run inetmgr.exe.
  12. Under the root IIS node select the Management Service.
    ManagementService 
  13. Stop the service.
  14. Select “Enable remote connections”
  15. Select “Apply” and “Start”.
    EnableRemoteConnections

The above steps will allow administrator accounts to publish to this server. If you are testing .NET 4.0 Beta 1 Web Applications you will need to install the framework on the machine you are publishing to or un-packaging on.

Ben Byrd | SDET | Visual Studio Web Developer

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • In this blog post I will explain how to get and install the Microsoft Web Deployment Tool, so you can

  • Thank you for submitting this cool story - Trackback from DotNetShoutout

  • Thank you for submitting this cool story - Trackback from progg.ru

  • Looking forward to trying out the packaging. What's the story when you have a webserver running something like Plesk? Is Microsoft working with control panel developers to offer integration?

    We seldom work with IIS 7 directly, only when changing global server settings. We create domains in Plesk, which creates AppPools and Applications in IIS 7 in the background. What are your thoughts on that?

    Thanks!

  • 2.0 beta, it give us lots of new addons. We can even use it to crate a WordPress website! very cool

  • Hi Mike,

    We are working with Control Panel vendors and hosters to get broader adoption of Microsoft Web Deployment Tool.  You may want to ask your hoster if they have plans to support it.  DotNetPanel, which is a control panel similar to Plesk recently added support for this.

    As a workaround in the meantime, you can use the InetMgr interface as described above to remotely connect to an IIS server and install applications via it, and then use Plesk or another panel to do additional tasks.

    Omar | Visual Web Developer

Page 1 of 1 (6 items)