I've been using unit tests for years, and I started using Resharper to run them as soon as Resharper offered support. We use nunit V2.7.
Today when I needed to run a unit test with the debugger. an exception is raised in the resharper task runner code before it gets to my code. The test runs and passes if I do not use the debugger. VisualStudio posts a managed debugging assistant which says:
The assembly named 'JetBrains.ReSharper.TaskRunnerFramework' was loaded from 'file:///C:/Program Files/JetBrains/ReSharper/v3.1/vs9.0/Bin/JetBrains.ReSharper.TaskRunnerFramework.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies..
Here's the last three calls in the stack:
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskRunnerHostBase.GetRunner(string runnerID = "nUnit") Line 50 + 0x18 bytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskRunnerHostBase.DeserializeTask(System.Xml.XmlNode element = Cannot evaluate expression because the code of the current method is optimized.) Line 100 + 0xc bytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskRunnerHostBase.DeserializeChildren(System.Xml.XmlNode element = Cannot evaluate expression because the code of the current method is optimized., System.Collections.Generic.ICollection<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode> nodes = Count = Cannot evaluate expression because the code of the current method is optimized.,
JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode parent = null) Line 85 + 0xb bytes C#
I am running
resharper version 3.1.584.3