I've put 3 votes on this and on
The .NET ecosystem is diversifying, becoming competitive and growing in new directions (i.e. xplat). Limiting ncrunch to Visual Studio is quite disappointing and I'm willing to bet, limiting your business in the longer run. The pace of VS code and Rider is rapidly catching up with VS and will soon leave it behind, with it's burden of legacy support.
The early adopters, the same people that helped bootstrap ncrunch when _it_ was new kid on the block, have jumped. The early majority is not far behind. VS now has it's own continuous tests and I don't doubt that Jetbrains one will improve and will work xplat (for xplat projects).
> impossible to carry with the existing structure of the NCrunch business.
Then you need to re-tune this. From an outside perspective, a partnership / co-development sponsorship with JetBrains to bring ncrunch to Rider makes sense. While it competes with their own dotCover/continuous tests (which is not a patch on ncrunch, _yet_) from their perspective it would reduces barrier / friction of Rider adoption for NCrunch users who are "stuck on VS". Just a suggestion.
Anyway, you need to consider your position on VSCode/Rider carefully. Not supporting will create a gap and a competitor will fill it.
Adding a menu button to the NCrunch Tests window tool bar would be very useful.
Integrate or be replaced.
So... I guess this must be bumping up the priority list now :)
Some of the tools windows being launchable & standalone also would be nice.
Yeah, nails battery life on-the-road.