Weird nuGet issues when NCrunch enabled and reloading a solution

Hello! I have a weird error I've encountered (and it's really only recently just started doing this)... Where when I have nCrunch enabled and I load my solution -- it says certain projects nuGet configuration is invalid... if I manually unload and reload the particular project, it starts working... Also when performing updates with nuGet with nCrunch enabled, it says certain assemblies are in use and can't be removed without a restart (like EF). This forces me to restart VS to 'fix' the in-use assembly, and then I end up with the problem above.

The work around I've found is to disable nCrunch while doing nuGet configuration and then re-enable after all is said and done, but I didn't know if there's some setting I'm missing that will help with this issue?

I appreciate any thoughts you might have...

Thanks
Chadwick

PS I'm using VS2015 Community, with nCrunch 3.7.0.7

Hi Chadwick,

Thanks for posting!

Much of the synchronisation handling around projects and Nuget was adjusted in NCrunch v3.8. I recommend upgrading to see if this helps.

I am aware of a race condition that can cause a clash between VS trying to perform restore action on projects at the same time as NCrunch is loading them. In my tests, this has only appeared very rarely, but it is on the list of things to address.

I always recommend disabling NCrunch when performing a Nuget update. This is because Nuget sets off a cascade of different parallel actions that are extremely difficult to reliably track using any integration code, so NCrunch cannot properly respond to these actions or get out of the way in time.

Thanks... Will do!