Disabling modules via configuration about elmah HOT 8 OPEN

How is this different than simply commenting out the relevant sections/elements 
in 
the configuration file to disable the functionality? What is the major benefit 
of 
being able to leave a component in the pipeline yet have it disabled? Granted 
it's 
easy to add, but still, it would be nice to understand the strong case for this 
overload.

I just like to be able to enable/disable things via configuration attributes 
instead 
of the comment out. It was easy to add and I like to do that as opposed to 
commenting them out if possible....

Either way....

[deleted comment]

I would also like to see this.

Personally, I use a custom utility to automatically generate multiple 
web.config files from a single template and this is a feature I have wanted for 
some time now as I cannot comment out a line with my tool, but I can change a 
property value to true/false.

[deleted comment]

I'd like this as well. 

Another solution would be to just allow an empty string for the "to" field in 
the configuration. I see that the code supports that (if the string is empty, 
it just returns out of the method. Right now it throws an exception if the 
field is empty.

Our situation is that we have multiple environments. We don't want to send 
emails in certain envrionments or from developer machines, but it's nice if the 
configuration files are mostly the same. In some projects I've been on, 
including this one, the various config files are managed with scripts and if 
they are very different then it gets weird. 

Thanks very much for a great tool.

This issue has been migrated to:
https://github.com/elmah/Elmah/issues/9
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.