That is what I figured as well.
However, I'm inclined to say that TC is not working as described in this article:
http://smartbear.com/support/viewarticle/11000 , where if the SSC provider does not support batch mode then the project files should be unbound.
I never had a problem with this in the 2008 MSSCCI, but I don't know if it supported batch mode either. Apparently the 2010 MSSCCI does not, but why would the project files be read-only.
Is this a red herring? Should I be implementing a custom build action to remove the read-only flag on the project sources? That seems to be the quickest way to overcome it, but I think that TC should be handling this on its own.
Anything I can do to verify my project configuration or build environment?
