For a while now on a large number of solutions that I enable NCrunch on, when I close visual studio and then open the solution again NCrunch is disabled.

If anyone knows some common reasons that could cause this please let me know, as this is starting to become very annoying.

Yeah on the solutions having the issue the file was readonly. Thank you for pointing me to the file and it being read-only.

I would think this could have been avoided if NCrunch would be simply detect this state and change to to be not a writable like ReSharper does for its settings file. Even visual studio will check out a file and make it writable if its in source control, and if its not and read only it will prompt me to change it to be writable. I am not sure how they became read-only, however I would think VS did something as the files are not even checked in.

I would think the use case here is that a user triggers a change in the NCrunch UI which requires a setting to be written, that the users expectations are that it will be persisted if no error occurs on closing the dialog. That the user would expect NCrunch to either simply make the file writable to make the change, or if its checked in check the file out and make the change. If you are not comfortable with those automatic choices then NCrunch could prompt the user for permission to take one of those actions when they close the dialog.