pete
My feedback
-
3 votespete
shared this idea
·
-
2 votespete
shared this idea
·
-
1 votepete
shared this idea
·
-
102 votes
-
217 votes
An error occurred while saving the comment An error occurred while saving the comment pete
commented
NCrunch is THE ONLY reason I stick to Visual Studio.
I hate VS and will leave it as soon as NCrunch works with Rider or Rider does Continous Testing well.pete
supported this idea
·
-
16 votes
An error occurred while saving the comment pete
commented
I fully support this idea.
IMHO that's the right way to move forward.
It's the only good future for NCrunch. -
16 votes
IMHO Damian Hickey described it perfectly.
Also the suggestion to partner with JetBrains is a very interesting idea that you should seriously consider IMHO.
Another option is to open up the "protocol" for other to implement the UI they want for tools they use. I'm sure that VSCode people would be very happy to do it and JetBrains IDEs have a lot of plugins as well.
I'm aware this imposes some limitations on your work and future NCrunch development, but it might be a good choice regardless of those.
From your forum response I'm guessing that you did couple NCrunch to VS too much and that's probably something you should fix ASAP in this changing landscape to continue to have success apart from keeping up with testing framework to make NCrunch work well in the meantime.
At the moment NCrunch is the best tool of its kind so IMHO you should not feel the need to introduce a lot of new features and use this time to ensure that NCrunch is safe for the next couple of years.