The Demise of Xcopy Deployment
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
One of the great features of .Net when it first released was Xcopy deployment. No more .dll registrations, just copy the files to the web server. While this was a great feature for Microsoft developers, new problems emerged, specifically around managing web.config. Sections like connection strings and custom errors need to be managed between environments, which meant many copies of the files or scripts to change them. Other necessary steps, like managing permissions and IIS configuration were still outside the Xcopy process. A recent tool, MSDeploy, is now integrated into Visual Studio 2010 and makes managing these issues easier. Besides web.config, MSDeploy also manages file deployments and synchronization, ACLs, and IIS settings. If your deployments have multiple steps, need ReadMe files, or can’t be done by someone outside your team, you need to learn MSDeploy!
- 1.The Demise of Xcopy Deployment
David Truxall, Ph.D.
Developer – Troubleshooter – Trainer - Consultant
Visual Studio 2010
Web Platform Installer
Visual Studio 2010
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
Remember Today’s Password: Elastic Syntax
At Publish, not at Build
msdeploy.exe -verb:<verbName> -source:<provider>[=<pathToProviderObject> [,<providerSetting>=<providerSettingValue>]] [-dest:<provider>[=<pathToProviderObject> [,<providerSetting>=<providerSettingValue>]] ] [-<MSDeployOperationSetting> ...]
<Exec Command='"C:Program FilesIISMicrosoft Web Deploymsdeploy.exe" -verb:sync -source:contentpath="$(DropLocation)$(BuildNumber)ReleaseSite" -dest:contentpath=ESTSERVERSite' ContinueOnError="false" />
Configure IIS Management Service
Open firewall port (8172)