Hi, yes, I do agree. The current approach is limited by the way in which the VS integration is working at the moment. I expect this will change in future.

When you say that the configuration manager does consider them being unloaded, are you saying that they are simply not accessible at all in this dialog? This is not the intended behaviour, even with the current implementation approach. Are you seeing this consistently across all solutions? Can you make it happen with a new dummy/test solution?

Thanks! I've now reproduced this issue. I will see what I can do to fix it. Meanwhile, to work around this, I'd suggest reloading the project in VS with NCrunch disabled. You can then find the project in the configuration window and set the 'Ignore this project completely' setting to True, then unload the project again. The next time NCrunch initialises, it will ignore the project and you won't need to wait for the timeout.