Hi, thanks for posting.

NCrunch monitors for VS builds via an in-process event. We don't have anything in NCrunch that can be used to create the kind of behaviour you are after ... but there may still be a way to get what you want, depending on what your script is doing.

Under normal circumstances, a build of the solution should not trigger NCrunch. This is because NCrunch is only supposed to listen to changes in the projects that would require them to be rebuilt. It may be that your script is making an avoidable file system change that NCrunch is responding to unnecessarily.

Try turning on your 'Log to output window' setting, and set your 'Log Verbosity' to 'Medium'. Keep your NCrunch VS output window open so you can watch the logs, and try running your background build script. NCrunch should report in the log which files it's reacting to. Knowing what is triggering NCrunch may give you opportunities to prevent the triggering entirely.