Thanks for the prompt reply.
Re: extensions. We have written our own extensions as well as making use of extensions from 3rd parties. It seems to me that your answer is the approach that we use when dealing with the 3rd party extensions. We use the same 3rd party extensions for all of our projects/suites. We never have to deal with 3rd party extensions via TC's [Tools]>[Options]>[Engines]>[Script Extensions] page because they don't change very often and can be stored in [...\Bin\Extensions\ScriptExtensions] as you said. That's easy.
However, it's a different story when it comes to our own extensions. We generally have multiple sandboxes on our machines. One sandbox may contain the current release version of our projects/suites and one (or more) sandboxes may contain projects/suites that are under development. Each sandbox is meant to be "self-contained", so each has its own version of our extensions. We have to use TC's [Tools]>[Options]>[Engines]>[Script Extensions] page to specify where our extensions are. Every time that we switch from one sandbox to another we need to go to the [Script Extensions] page and change the path to our extensions folder in the sandbox that we are currently working in. If we forget to do that then we can easily run into problems since the extensions being used belong to a different sandbox than the one that we are working on. The [Script Extensions] page applies to TC and not specifically to the currently loaded project/suite, so switching to a project that is in a different sandbox does not automatically switch to the extensions that are found in that sandbox.
Copying our extensions to [...\Bin\Extensions\ScriptExtensions] is not the answer (unless we set something up to copy the extension files from the sandbox to [ScriptExtensions] every time that we switch sandboxes. Yuck. We'd also still have to somehow reload/refresh the extensions after the copy, which would probably have to be done manually via [File]>[Install Script Extensions...]>[Reload].
I don't think that the [Script Extensions] page even allows you to use relative paths (though I may be mistaken). I guess that the question would be "relative to what?". If you change projects then you are changing your location and wouldn't that then necessitate recalculating the provided relative-path to your extensions? Since it is TC-related instead of project-related, I would think the relative path (if allowed) would have to be relative to the TC-folders rather than the project-folders.
When our clients install our projects/suites, they create their own sandboxes. We have no control over (and don't want to try to limit them) what the sandbox paths are. They also may have multiple versions of our tests (since they are testing multiple versions of their software). It would be wonderful if there were some flexible way to have the tests run without them having to tweak TC first so that our extensions could be found.
So, my original question was trying to find some way to automatically adjust the location where TC expects to find our extensions when we switch/load projects. It does not sound like TC can do this though it seems like it is a logical concept to investigate.
