Forum Discussion
markbain
15 years agoOccasional Contributor
I am reading the Help that you suggested I look at. However this paragraph suggests that this will not be useful:
When you add a project to source control from TestComplete, the latter saves the local file paths to the project (or project suite) files. If you check out the project (or project suite) using TestComplete on another computer, TestComplete will replace the local paths in the project (project suite) file with the paths relevant to this computer, so when you open the project on your computer again, the project link to source control will be broken and you will have to rebind the project to source control.
If I am reading this correctly, with many people checking out the project (saved in Source Control) my project will continue to keep breaking and I will have to continually 'rebind' it. This doesn't sound very 'user friendly'.
When you add a project to source control from TestComplete, the latter saves the local file paths to the project (or project suite) files. If you check out the project (or project suite) using TestComplete on another computer, TestComplete will replace the local paths in the project (project suite) file with the paths relevant to this computer, so when you open the project on your computer again, the project link to source control will be broken and you will have to rebind the project to source control.
If I am reading this correctly, with many people checking out the project (saved in Source Control) my project will continue to keep breaking and I will have to continually 'rebind' it. This doesn't sound very 'user friendly'.
Related Content
- 2 years ago