.net - Mistake proofing web configuration -
After a long and tedious problem solving ritual, it was found that '/' is unavailable in a URI for API configuration. Reason for error.
http://ab.com/xyz instead of http://ab.com/xyz/
Except all the other environments were properly configured, add frustration.
There are some sensible ways - automatic or not - by mistake this evidence?
I have not done any pure coding, but I am under the assumption that .net applications are usually XML is used as a syntax for them. The configuration file suggests that you may want to use the XML Schema verification engine to automate some semantic check on the contents of the configuration files.
Some of the Wikipedia articles are some of the more famous.