3 comments

  1. I have seen this as well. I experienced it when running unit tests on a custom IXmlSerializable class – so in my case, it seems to be tied to the Xml stream objects – and of course the Xml parser still does use Xml under the hood.

    Howard Dierking Beantwoorden

  2. Where you ever able to figure out what was causing the error? If Howard found it under the xml parser that might explain why I recieved it under the resource manager. If you have any thoughts I would love to hear them.

    James McKee Beantwoorden

  3. I don’t remember exactly the unittests anymore, but I certainly was using the dll.config feature of NUnit. So maybe it was related to Xml too.

    I haven’t had this message anymore since that day of this posting though…

    Raimond Brookman Beantwoorden