Mike and I work for the same company, and are dealing with the issue of saving TestComplete project suites and projects. So many files are changed each time that are completely unrelated to the single script you are attempting to debug. If you attempt to reload the project from the repository, you get many conflicted files from Subversion. I suspect the issue would be the same for any other source control repository (like ClearCase).
After I have made some changes to my local copy of the repository (changing a script as I debug, and rerunning it), I have log files, objects, and alias that are now in conflict when I attempt to reset TestComplete to a known location. When the conflicts exist from the source control system, the project is unavailable to TestComplete. I am now dead in the water.
What is the solution to archiving TestComplete projects in a source control system?