Thanks for the reply. I understand how to get the test framework to load a config file, and the first test does just that. It succeeds on both platforms. The second test does the same exact thing, only it makes a call to HttpUtility first, and this seems to trip up the ConfigurationManager, but only under mono. Under MS .NET, both tests succeed in loading the configuration and both pass, but under mono, the first test passes and the second test fails because once a call is made to HttpUtility, the ConnectionStrings are replaced with the defaults from the ASP.NET stack. This seems like very odd behavior.
On Friday, August 9, 2013, Charlie Poole wrote: > Each test framework has it's own requirements for where a config file must > be located and how it should be named in order to be loaded and used. >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
