Support for ReSharper 8.1

[mhoyer]

Are there any plans on also supporting R# 8.1?

I already tried to migrate AgUnit on my own, but didn't get to any result yet:

mhoyer@a92d0d3

I could already fix the Jetbrains references and the two errors in SilverlightMsTestMetadataExplorer.CreateMsTestElementFactory(). But now I got stuck with UnitTestRunExtensions.GetSequences(). This method is magically trying to resolve private "mySequences" field on UnitTestRun instance through reflection. This field now does not exist anymore. I am not quiet sure if such approach really is what Jetbrains intended to do. ;-)

I also tried to replace this reflection part with using original Resharper API use. For instance:

IUnitTestRun.Elements
IUnitTestRun.GetTasks()
UnitTestRun.GetElement()

As I don't know what and how all the wires are connected, I'd like to have some advise on this.

[sdekock]

Most of the reflection is/was a necessary evil because the required extension points aren't/weren't there. This current code base was (re-)written for R#7.
In R#8 a lot of changes were made to handle Modern/Metro testing using the built-in visual studio MSTest runner instead of the custom one from JetBrains. This introduced new extension points and internal changes.
There may be better ways to do this now in R#8(.1) than there were with R#7.

You'll have to look through the decompiled code of the R# assemblies (using navigate to decompiled sources in ReSharper) ...

Concepts:
Element = reference to test assemblies, test classes, test methods in the code
Session = a tab in the unit test sessions window
Launch = one launch of a specific unit test session (when you press Run/Debug)
Run = Group of tasks/sequences (with the same version of .NET framework, ...) in a launch
Sequence = A non-hierarchical list of tasks to execute, usually one per test method: list with test assembly, test class, test method
Task = a step to execute during the unit test run, usually these map one-to-one with elements (assembly task, class task, method task)

Sequences are joined afterwards to build a task tree which is executed hierarchically in the task runner.
AgUnit walks through all sequences to see if they contain silverlight unit tests and injects a 'SilverlightTask' as the first element. This way it can inject itself as the root task node in the task runner.