I have a dual-monitor setup, and I usually have NCrunch's Tests window on the secondary monitor. This setup has been working fine for a while, although NCrunch does seem to struggle to detect the correct size of the screen and every time I open Visual Studio I need to manually "Restore Down" + "Maximize" NCrunch's window in order to get NCrunch to show the content correctly. Otherwise, the right pane is truncated and the content is not visible
The above is an issue that is annoying but not a big deal.
However, since my license expired, NCrunch is consistently crashing Visual Studio as soon as click the "Restore Down" button. Visual Studio goes unresponsive and I need to close it down and start it again.
This issue is a big problem because, combined with the original problem, it does render NCrunch unusable.
And I can confirm that setting the scaling to 100% on the primary monitor and restarting Visual Studio stops NCrunch from crashing, and it also solves the truncating problem.
An alternative solution would be great though. I do need the scaling in my primary monitor :-)
emsurgecto wrote:And I can confirm that setting the scaling to 100% on the primary monitor and restarting Visual Studio stops NCrunch from crashing, and it also solves the truncating problem.
An alternative solution would be great though. I do need the scaling in my primary monitor :-)
Thanks for confirming this. We don't support dynamically changing the scaling on the NCrunch UI by dragging tool windows between screens with different scaling. This is because of limitations in the underlying toolset (winforms). However, it shouldn't crash the IDE. Could I trouble you to try bringing out the crash with another VS instance debugging VS while it crashes? This should allow you to provide us with a stack trace. Unfortunately newer versions of VS make it much harder to get this stack trace now (it used to be in the event viewer).
And a clarification: I don't drag the window to the other monitor. It's already there when it opens, because it was there last time I closed Visual Studio and it seems to remember its position.
emsurgecto wrote:
And a clarification: I don't drag the window to the other monitor. It's already there when it opens, because it was there last time I closed Visual Studio and it seems to remember its position.
Understood :) I just wanted to be clear that we can't make it as perfect as we want it to be. Regardless, a crash in any case is not an acceptable outcome.
Unfortunately, setting the scaling back to 125% and restarting Visual Studio does not reproduce the issue anymore. Which is good news, in a way, although it means I can't send you the stack trace now.
I'll keep an eye out and if I see it again I'll make sure to post the stack trace here.