We don't currently have support for scheduled deployments in the Deployment Manager UI (it's mentioned in this uservoice suggestion
). However, you can get the functionality you want by using Windows scheduled tasks to schedule DeploymentManager.exe
operations to automate deployments. The process exit code will be zero if the deployment suceeds, non-zero otherwise. You can also make deploymentmanager.exe
output the full deployment log by adding the -l
command line flag.
DeploymentManager.exe is documented here
, and you can also get full documentation on the available command line arguments by running
Using variables to control all sections of .config files
- Code: Select all
We were actually discussing that one in a planning meeting this week. We're not sure how to strike the balance between simplicity and flexibility of configuration. It would be really helpful if you could tell us what configuration elements you're trying to change, and how you'd like to be able to use variables to make those changes.