Hi Thomas,

This is by design, because of changes MS made to the solution handling in VS2017.

Under VS2017 lightweight solution mode, it's normal that most projects won't be loaded when the solution is first opened. Instead, VS will load them on demand. Because VS also loads projects asynchronously from VS2012 onwards, there is now no state under which the actual 'opening' of the solution can reliably be considered complete, because this is a process that can run over the lifetime of the dev session and may never actually complete.

This means NCrunch just needs to work with the data it's given as soon as this data becomes available. NCrunch considers a solution 'open' from the point where the first project is reported by VS, and will load projects from disk if necessary, resynchronising with the IDE if it reports more projects being loaded into memory. Reliably synchronising with the VS project system is a hellishly complex thing that seems to get harder every year.

Because NCrunch performs all its activity in low priority processes, I would hope that its initialisation during solution opening wouldn't interfere with the IDE too much. Have you tried timing the opening of the solution with/without NCrunch enabled and comparing the times? I don't doubt your CPU and disk activity will spike considerably though.