nunit-core team mailing list archive

[erik hooper <erik.hooper@xxxxxxxxxxx>]

Sorry for the delay. I finally have some code that will repo this issue.
There is client and a server that using .net remoting. I have a system
test that uses the same call to send a message to the server. If you
start the service you should be able to run the test and see it pass. If
you comment out the line of code (line 25) in the test that calls
FreeNamedDataSlot you should now see the test fail.

** Attachment added: "RemotingException.zip"
   https://bugs.launchpad.net/nunitv2/+bug/1084181/+attachment/3527012/+files/RemotingException.zip

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