Team Build Solutions -- missing the obvious.
On the outside chance that I'm not the only that missed the obvious:
I've worked on-and-off for months now with teambuild projects and it is a bit of slow process given the need to check-out and check-in the .proj, .rsp, and .xml everytime you want to test a change to your script. In addition, it's a pain, because every time I go to save I always get nagged that my file is read-only.
When you're developing other code, the development enviornment automatically handles the check-out for you on edit, so I'm just not in the habit of being explicit. Finally, it occured to me to just add these items to a solution and save the solution in the TeamBuildTypes folder along with those files and now it works great.
It seems like a small thing, but it's just a hassle I'm glad to have behind me.