Where in the NUnit code is this occuring... that is, what does Resharper actually call into.
My thought is that we could clear the context when we no longer need it. Charlie -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/1084181 Title: TestExecutaionContext SerializationException Status in NUnit V2 Test Framework: Confirmed Bug description: Nunit v 2.6.2.12296 throws a SerializationException because TestExecutaionContext is not marked as Serializable. Looks like TestExecutaionContext is calling CallContext.LogicalSetData("Nunit.Framework.TestContext",current.contextDictionary) however contextDictionary=> TestExecutaionContext is not Serializable. This prevents remote calls. You will get a System.Runtime.Serialization.SerializationException : Type 'NUnit.Core.TestExecutionContext' in Assembly 'nunit.core, Version=2.6.2.12296, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77' is not marked as serializable exception. You can work around this by calling CallContext.FreeNamedDataSlot("NUnit.Framework.TestContext"); but is ugly and might break your expectation about what is in the context? -Erik To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/1084181/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
