Re: TC 14 and TFS 'project node is write-protected'?
SmartBear Support has emailed us a patch to TestComplete 14 as a possible solution to this problem.
This overwrite issue also causes another issue with TFS. When a file is overwritten it is not checked out so the server copy is not updated during check in. Now your local changes are not in sync with this server. This causes problems when the code is shared to another user/pc through TFS. I suspect we never encountered this before because we were setup with local workspaces instead of server workspaces prior to our upgrade of TestComplete and TFS.
From SmartBear suppot, "The issue is caused by the fact that files have the "write-protected" attribute enabled. The TFVC subsystem needs to write its key to the project file to provide TestComplete with the information that this project is added to TFS. You need to allow modifying the files when opening the project (click "Yes to All" when you get the message that files are write-protected). Perhaps, it will be easier to disable the "write-protected" attribute for the files at all. I suppose you can contact your IT department for this. Also, we suggest installing the patch below which fixes some critical issues when working with TFS. Also, the patch should allow editing a project node without the SCC key. "....
We will evaluate these instructions and the patch and post back with our results.