Closed ramijarrar closed 8 years ago
I looked over the implementation for loading the custom web.config and it is performing a check within the specified directory to ensure that a file named 'web.config' does in fact exist. This is probably safer/more intuitive than automatically renaming a potentially incompatible file so I think it is best that I stick to renaming the file myself and then loading it in the tool.
I am using different web.config files for staging/production which are stored side-by-side in version control. In order to easily differentiate between the two, I prefix each file-name descriptively. During a deployment, when I point the tool to these files in the 'install' step, it would be helpful if their names were automatically corrected to save me the effort of doing this myself :)
I couldn't think of any potentially harmful implications of adding this functionality, but would be open to hear your perspective on this.
Thanks!