Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Option to delete XML config transforms after applying #834
Lingering .config files cause issues for some applications.
Given this file system:
Assume we deployed to Prod. We would have run Web.Prod.config, and Web.Release.config. It's obvious those files should be deleted.
But how can we tell that Web.config should be kept, while Web.Dev.config shouldn't? I.e., how do we know which files are transforms and which files aren't?
Will the decision be based on the existence of:
On the root node?
Hello guys, is there any chance of re-opening this issue? :)
The step template is a great workaround (thanks for that!) and I'm using it, but having to have an extra step on every single deployment process is very annoying.
I'd love to have a checkbox on the "Deploy a NuGet package" step, that matches all .config files that match
I have very easily achieved this using this script (based on the namespace as @PaulStovell suggests):
Note that it requires the files to be named *.config and the root element to be called "configuration". So only config transform files for now. This could be easily changes though.
Export of script template JSON: