Ability to push new web.config
We push our web apps to IIS using Octopus/Octopack. Frequently we make transform errors in web.config (forget to include a transform or have wrong value in transform). When this happens, it's painful because have to rebuild/repackage/redploy the entire web app. In this scenario, new code is not needed just new web.config with corrected transforms. Would be nice if Octopus could help us push new config to existing app instead of having to push whole new app.
This goes against how we at Octopus consider deployments should take place. As soon as you have changed parts of your config that cant be dealt with by purely updating the variables then it should be considered a new package and tested accordingly. While its not something we would ever prevent users from doing, it is unlikely to be something we provide for as a first class concept
Here is another use-case : We sometimes change some app settings for various reasons including but not limited to :
1. App settings value change for short period
2. New end user url's change only for certain environment in web.config
It would be better if Octopus allows to deploy only web.config or changes in web.config or log4.net
I'm assuming you use TFS/Msbuild. You could solve this by creating a separate build and build definitions that only packages web.configs
Setup a "Deploy Configs" project in Octo, use the PowerShell scripts Deploy.ps1 etc or an extra PowerShell step to update the existing IIS web.configs.
Or even better if you can write checks so that the build fails if transforms are wrong/missing.