nunit-core team mailing list archive

[erik hooper <erik.hooper@xxxxxxxxxxx>]

That is correct we are making a .net remoting call during the TestFixtureSetUp. However I can not repo without resharper. I ran using the nunit gui and everything ran fine. We don't even reference nunit.core within the test project. 
Also there are cases within the tests(these are system tests) that we DO make calls to the remote objects outside of the test setup, there is a good possibility that this will also give the same error. But resharper IS required to see the issue. I am not sure what they so on their end.

As far as a stack trace that was pretty much it. There isn't a lot to add it comes for the Testsetup method and the first remote call.
-Erik

-- 
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