Your official information source from the .NET Web Development and Tools group at Microsoft.
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.
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:
Microsoft Web Deployment should now be installed and useable by the command file generated from VS 2010 for deploying.
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.
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
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?
2.0 beta, it give us lots of new addons. We can even use it to crate a WordPress website! very cool
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