Team Foundation Version Control Naming Syntax, Conventions, and Limitations
Team Foundation version control has naming syntax, conventions, and limitations.
Team Foundation version control has the following naming syntax, conventions, and limitations:
Check-in note names can be up to 64 characters long.
Check-in policy names can be up to 256 characters long.
Label names can be up to 64 characters long.
Workspace names can be up to 64 characters long.
Shelveset names can be up to 64 characters long.
Most names in Team Foundation version control cannot begin or end with spaces or tabs. Any character can be used for names or labels, except the following:
Angle brackets (< >).
Forward (/) and backward slash (\).
Question mark (?).
Quotation mark (").
A dollar sign ($) cannot be the first character in a file name.
Label names cannot contain (@).
Workspace and shelveset names cannot contain (;).
Check-in comments can be up to 2GB.
Check-in note values can be up to 2GB.
Label comments can be up to 2048 characters long.
Shelveset comments can be up to 2048 characters long.
Workspace comments can be up to 2048 characters long.
Files and Paths:
Server paths can be up to 259 characters.
Local file paths fall within Windows limits of 259 characters long (including the file name), and 248 for a directory.
Files in the Team Foundation version control server have no size limit.
The total size of content in the Team Foundation version control server has no limit.
A namespace in Team Foundation version control is a logical grouping of unique item names.
Names in Team Foundation version control refer to the file system pathnames of items.
Items are the principle objects Team Foundation version control and represent either file or directory pathnames.
Each item has a unique numeric ID that distinguishes it from all other items in version control.
Each item may have multiple pathnames that specify multiple locations on client and server computers. For example, each item may have a path in one or more of the following namespaces:
Local Space This indicates a path in the local file system which is mapped to a version-controlled item on a Team Foundation server.
Committed Space This indicates the server path of an item checked in to version control on a Team Foundation server.
Pending Space This indicates the server path of an item after you have checked in all currently pending changes.