IT:AD:WebDeploy
Summary
Standard MSI based web deploy packages were dropped from VS2012. `MSDeploy` (in the form of `WebDeploy`) is now the preferred way to deploy *websites* (Windows Services, Console Apps, etc. are better suited with different deployment strategies).
WebDeploy creates Deployment Packages, that are combinations of: * zip * parameter file * a default bat file to run one of the IT:AD:MSDeploy statements.
- This can be replaced with a custom bat or IT:AD:Powershell script to run more powerful scripts.
Facts
- IT:AD:WebDeploy creates Deployment Packages, that are combinations of zip + parameter file + bat file to run IT:AD:MSDeploy statements.
- WebDeploy is not a technology/command in itself – but a packaging and batching of IT:AD:MSDeploy statements (see http://www.asp.net/web-forms/tutorials/deployment/web-deployment-in-the-enterprise/deploying-web-packages for confirmation of this).
- IT:AD:WebDeploy provides the ease of IT:AD:Visual Studio integrated tools – but only a small fraction of the power in MSDeploy.
- It's easy to deploy over the wire from a dev VS to an ST server in the same network, but will rarely get approval to deliver the same way to a remote QAT or PROD server.
- IMPORTANT: A WebDeploy package is intended to be configured per Build Configuration, refined with Parameters.xml file per target server.
- Packages can be developed and deployed from the CommandLine (IT:AD:WebDeploy:Publishing)
- It's important to understand that the ease of the IT:AD:Visual Studio
Publish...button hides the power that comes with knowing how to build deployment scripts by hand using IT:AD:MSDeploy commands.- ie: do take the time to know the Syntax
Resources
* http://www.asp.net/web-forms/tutorials/deployment/web-deployment-in-the-enterprise/deploying-web-packages * MSDN Summary * My kind of good notes * How to write a website to manage a server at a distance: http://bit.ly/yD2Awp