I've looked quite a bit more into this today. It can be reproduced simply with
this (nothing to do with unit tests or shadow copies as you said, just happens
when something in System.Web tries to read the configuration):
class MainClass
{
public static void Main
This is the exact same problem, yes. So from your last comment on the pull
request:
> when running inside a unit test, Mono.Web.Util.SettingsMappingManager.Init()
> doesn't manage to make the _instance not null, because mapper.HasMappings
> ends up being false (and this doesn't happen when run
On 10/08/13 10:40, "Andrés G. Aragoneses" wrote:
...
I have a patch that fixes it, which I proposed in a pull request:
https://github.com/mono/mono/pull/725 .
Wrong URL, I meant this one: https://github.com/mono/mono/pull/643
___
Mono-list maillist
This is not related to NUnit. This is exactly bug 11972 which I filed
here some months ago: https://bugzilla.xamarin.com/show_bug.cgi?id=11972
The problem lies in the fact that whenever any code inside the
System.Web assembly tries to read the configuration, it replaces the
System.Configurat
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 on
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. Those
requirements are necessarily different from how .NET normally locates
config files because following the .NET rules would load the config for the
te
I ran into an issue several months back where my code could not find
ConnectionStrings while running my code in NUnit under mono, however, I was
having trouble making a simple reproducible test case. Now I have one, and I
suspect that it is not an NUnit issue, as the same thing happens under xU
