Script extensions are a very useful feature of TestComplete, allowing end users to create their own custom objects, checkpoints, keyword operations, etc., for use in their automation projects. We us...
I considered using that method to drop in the files. However, I'm not certain how that would work. The TCX file needs to either be in the script extensions folder of the instance of TestExecute or in a user designated folder (Tools | Options | Engines | Script Extensions). That user designated folder won't work because CBT doesn't allow us to alter the TestExecute configuration.
To link to the TCX file in the default TestExecute folder and bring that in as an external file in TestComplete MIGHT work... but that seems to be a bit "round the back door" and I'm not certain of the impact. Additionally, as you point out, it means that we'd have to make sure that our extension folders and such are properly set up to use the default, that our source control of the TCX file points to that folder, etc. Not sure I want to go that route. Hopefully, the SmartBear folks can give us something a bit more in this.