Well into a VS/test session, the Program Compatibility Assistant popup appeared indicating nCrunch.TestHost.x86.exe as the program. I Had just opened up NCrunch Configuration and was starting to change some settings (log to output) around this time, and while tests were running.
While copying & pasting the window for thie post, another "Unhandled exception ... Thread was being aborted" popup appeared.
Also, ono ne of my systems installing 1.45.12 failed, so I rebooted and it worked. Not sure if something less than a reboot would have done the trick.
Daily Usage Issues
1.45.12 -- Windows detected that this program did not run correctly
Started by BKStrelioff on 6,107 views
Remco NCrunch Developer
#3961
03 Apr 2013 21:58 UTC
Is there any code you have running under test that might trigger the compatibility mode assistant? (i.e. are you interacting with any deeper level or legacy APIs?)
From a couple of the other issues you've reported earlier, I'm wondering if for some reason your system is having issues with the hosted task runners. There's a configuration setting that you may want to try to see if this helps. If nothing else, this may be useful in order to narrow down the source of instability. Try setting the Use hosted task runner global configuration setting to 'False'. You'll notice that the NCrunch task runners will run under different names, but there should be no functional difference.
From a couple of the other issues you've reported earlier, I'm wondering if for some reason your system is having issues with the hosted task runners. There's a configuration setting that you may want to try to see if this helps. If nothing else, this may be useful in order to narrow down the source of instability. Try setting the Use hosted task runner global configuration setting to 'False'. You'll notice that the NCrunch task runners will run under different names, but there should be no functional difference.
Post a reply
Log in to reply.