The only analogy I can think of for the machine.config is that it is to the .net framework that an agent is to the Matrix. It holds all the keys and it guards all the doors. Anytime I spend hours trying to figure why some form of unexplainable error has happened, the machine.config has the answer. A good example was today. I was helping my fearless user group leader Julia figure out why an exception was being thrown on a web service call:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
Julia figured out that her IE proxy settings were enabled, and that setting is system wide. This is what was causing the exception to be thrown. Searching through the machine.config I found:
<system.net>
<defaultProxy>
<proxy usesystemdefault="true" />
</defaultProxy>
</system.net>
All .net applications will use this same system wide proxy setting by default. She added usesystemdefault="false" to her app.config, and we were good to go.
11:46:14 PM 
|
