Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 33375 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 12640 [details]
Sample solution showing how when override config has invalid chars, default is used instead of exception being thrown
When the App.config file and/or its override file contains invalid XML, the expected ConfigurationErrorsException is not thrown.
This caused problems for us when in our scenario, the override XML contained a nil bit, and on Mono 4.2 on OS X 10.11 (this repros on 10.10.5 as well, so I'm assuming this isn't OS specific), the override key/value pair was ignored, and the original value was instead used. No exception was thrown.
On Windows, an exception is thrown immediately on startup.
When the App.config file contains an invalid XML, such as in the case of the nil bit, Mono ignores it and still uses the configuration value.
The expected behavior here is that some kind of XML validation occurs.