Although it is not recommended to use blanks in names for TFS team projects, this option is supported and therefore you can end up with a team project named like that. This would be a showstopper for using this particular team project for versioning database objects with Toad For Oracle 12.6, because Toad does not support team projects with blanks (spaces) in their names.
Note: I am using the Visual Studio 2013 Application Lifecycle Management Virtual Machine currently with TFS 2013 Update 3 and Visual Studio Ultimate 2013 with Update 3, where I have additionally installed the Oracle Demo DB locally (Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows (x64)) and Toad 12.6.0.53 with Team Coding 7.1 – Trial.
Scenario:
I created a new team project named “Name with Blanks”. I successfully used it to create a Team Coding Code Collection for handling procedures as shown in the following picture:
To perform an initial import of objects managed by this code collection, I used the action “Create new revision in VCS”. The generated list of scripts for corresponding objects was correctly created in the Create new revision in VCS tab.
The problem is that the values in column VCS project, which contains the path to the TFS server folder, were not correctly generated – the blanks in the team project name were replaced with underscores, like this: $/Name_With_Blanks/TOAD/XE/HR/PROCEDURE.
As the result of such a path, the export procedure does not work and gives the following errors:
“Could not validate VCS Project : $/Name_With_Blanks/TOAD/XE/HR/PROCEDURE. Check your VCS configuration before continuing.”
Finally, in the Toad Output window you get the following error:
“Output: Could not validate VCS Project $/Name_With_Blanks/TOAD/XE/HR/PROCEDURE.”
The solution is obviously to use TFS team project without blanks (spaces) in their names 
