Last week Ncrunch refused to start any tests in one of my solution. Tray icon was showing that he is building sthm, but there where no activities in Ncrunch Processing Queue. On test start NCrunch was hanging infinitely showing that he started the test, but actually nothing happens. That test is green and is perfectly executed in MSTest for 71ms.
Today I've moved to another solution and that issue with Ncrunch is still reproducing. I'm using VS2012 with Ncrunch 2.16.0.13. Windows 7 with autoupdates.
Well, I've installed some cryptography software which states to have no integration with Visual Studio. If I debug test then nothing happens. Icon is just infinitely circling.
Is it possible this has enabled FIPS on your machine?
I don't think the problem itself is related to VS itself - more likely it's something resident on your machine that is interfering with .NET processes. Do you actually see a test host .EXE launch when you try to run the test?
>I don't think the problem itself is related to VS itself - more likely it's something resident on your machine that is interfering with .NET processes. Do you actually see a test host .EXE launch when you try to run the test?
No. There are no test host .EXE processes. Only nCrunch.EngineHost45.x86 and several nCrunch.BuildHost40.x86
>Is it possible this has enabled FIPS on your machine?
What is FIPS?
I've managed to start tests. It seems that when Ncrunch is configured to use engine hosting strategy "x86SatelliteProcess" then it refuses to start on my PC. If I set "HostInsideIDE" then Ncrunch starts working.
Ok - this means that something on your system is preventing the engine host process from launching additional processes, but it won't interfere with the IDE.
Sorry, I'm at a loss to explain what in your environment could be causing this.
I'd suggest continuing to work with the engine hosted in the IDE. There are no plans to remove this feature and there can be some benefits to running the engine this way.