Hi, thanks for posting.
For a good number of years now, NCrunch hasn't contained any code that would instantiate a console window under windows. My guess would be that this is being triggered by a build step in your project that is creating the window in its own code. As such, the problem would be in your build system rather than NCrunch itself.
Unfortunately there isn't much I can do to help you with this problem. Azure projects aren't officially supported by NCrunch. I recommend looking to see if there are any updates to your Azure toolkit or whether there are any build steps you can safely disable using
NCrunch-conditional build behaviour.
Edit: I've had an idea that may help. If the build system contains code that insists on creating a visible window, there isn't much NCrunch can do to stop it. However, it IS possible to set up your environment in such a way that the build code will run under a different user profile. You can do this using NCrunch's distributed processing. Basically, set up a grid node on your local machine, transfer all the local processing to it (disable (local) in the Grid Management Window), then set this node to run under a different user account on your machine. In this way, you'll never see the window appear unless you run a test with the debugger attached.
