XmlException when error XML has been customized with new elements

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Check out ELMAH from the branch RB-1.2 (r737 at this time)
2. Open samples\Demo\Web.config.template in a text editor and change it to use 
XmlFileErrorLog instead of the pre-configuration of SQLiteErrorLog; save then 
exit editor.
3. Run demo.cmd to launch the demo web.
4. Generate an error through the demo web.
5. Go to the directory where the XmlFileErrorLog was configured to generate the 
error XML files and open one of them in a text/XML editor.
6. Add a custom well-formed element under <error>; save then exit the editor.
7. Return to the demo web to refresh/view the error log.

What is the expected output? What do you see instead?

Expect to see the error log display without any effect of the customization of 
the error XML. Instead, an XmlException gets generated along the lines of, 
"'Element' is an invalid XmlNodeType. Line 154, position 4."

Original issue reported on code.google.com by azizatif on 18 Oct 2010 at 11:00

[GoogleCodeExporter]

Original comment by azizatif on 18 Oct 2010 at 11:05

• Changed state: Started

[GoogleCodeExporter]

Fixed in r754.

Original comment by azizatif on 28 Dec 2010 at 10:24

• Changed state: Fixed