Comment 4 for bug 1203587

Hi Shawn,

The NUnit executor URI is in the NUnit code, so there's nothing to
reset. One hypothesis is that resharper is taking over handling the
context menu and is incorrectly invoking NUnit. However, this is just
a guess.

In any case, reporting the problem to JetBrains might get them to
fix it or, alternatively, to indicate what we need to change to be
compatible with them.

Charlie

On Sat, Jul 27, 2013 at 5:42 PM, Shawn D <email address hidden> wrote:

> Yeah, the workaround does the trick, though, of course this is not the
> ideal situation. Charlie, since I am not at all familiar with Visual
> Studio, are we sure this is a ReSharper issue because the error is
> reported when trying to run the tests via test explorer? If ReSharper
> sets the URI, could the test explorer reset it on activation? Any logs
> we can have to see the details of the failure to understand the issue
> better? Ideally we wouldn't have to disable ReSharper since its crucial
> for development as well. Any information would be appreciated. Thanks!
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/1203587
>
> Title:
> NUnit Test Adapter for VS 2012 cannot find tests when run
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunit-vs-adapter/+bug/1203587/+subscriptions
>