Problem debugging prig MSTests with ReSharper test runner

[andy250]

Prig is AWESOME. I have one issue though: when trying to debug the test with ReSharper 2016.3 test runner within VS2015 whole IDE freezes. I am using Microsoft Test Framework (Microsoft.VisualStudio.QualityTools.UnitTestFramework). Can I fix it somehow?

[urasandesu]

Currently, Prig doesn't support ReSharper 2016.3 test runner.

I guess that there is no such use case for the open source developer who uses Prig because ReSharper is too expensive -- yes, I am, too 😢

[urasandesu]

MEMO
To enable Prig in ReSharper, it turned out that I just change the filter that identifies target test runner in Prig.psm1 as the follows:

New-Variable ProfilerTargetProcessArgumentValue '(vstest\.executionengine)|(te\.processhost\.managed[^/]+/role=testexecution)|(JetBrains\.ReSharper\.TaskRunner)' -Option ReadOnly

However, ReSharper test runner will crash from I just doing that. The !analyze -v result
indicates that access violation occurs in clr.dll but I guess the real cause is different. Currently, I can't download clr.pdb so I have difficult investigations.

[zaitsman]

Any updates on this? ReSharper support is vital in some cases.

[urasandesu]

@zaitsman, I'm going to support ReShaper in v2.4.0, but it is limited. There is the known issue that test process exited abnormally when creating new AppDomain in a test case.