Visual Studio 2012
- TF201017: You don't have permissions to complete the operation. To create, modify or delete link types, you must have the ...
- TF201021: The topology is not supported. See http://go.microsoft.com/fwlink/?LinkId=74075 for the supported link type topologies. ...
- TF201022: The reverse name is not specified or is not supported. See http://go.microsoft.com/fwlink/?LinkID=72977 for link ...
- TF201029: The link type cannot be deleted. See http://go.microsoft.com/fwlink/?LinkId=74121 for more information on deleting ...
- TF201031: {0} is not a valid type of link. Check the spelling and capitalization. If you're not sure, use witadmin.exe to ...
- TF201032: The {0} link between work items {1} and {2} that you are attempting to delete does not exist. It may have been ...
- TF201035: Adding a {0} link between work items {1} and {2} would result in a circular relationship. To create this link, ...
- TF201038: Linked item does not exist or access is denied. See Work Item Permissions for Links (http://go.microsoft.com/fwlink/?LinkId=75624) ...
- TF201040: The 'LinkColumn' element requires the 'LinkAttribute' or the 'RefName' attribute, but not both. Specify either ...
- TF201044: The link type filter '{0}' specifies a link type that does not exist on the Team Foundation Server. Specify a valid ...
- TF201045: The link attribute '{0}' is not a supported link column. Specify one of the valid link column types, {1}, {2}, ...
- TF201046: {0} is not a valid link type reference name. User defined reference names may not begin with 'System.'. See ht ...
- TF201047: The {0} links control element is not supported. When the {1} attribute is {2}, that element cannot contain elements. ...
- TF201048: The links control filter contains an element for link type {0} that is not supported. That link type is not directed, ...
- TF201051: {0} is not a valid link type reference name. See http://go.microsoft.com/fwlink/?LinkId=80887 for more information ...
- TF201052: {0} is not a valid link type name. See http://go.microsoft.com/fwlink/?LinkId=80887 for more information about ...
- TF201060: The query on links element {0} is not valid. Use LeftQuery for the main query, LinkQuery for the link query, and ...
- TF201063: Adding a {0} link to work item {1} would result in a circular relationship. To create this link, evaluate the existing ...
- TF201067: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201067: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201068: The work item metadata cache is out of date. Refresh any cached work item metadata and try the operation again. ...
- TF201068: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201069: The work item metadata cache is out of date. Close Visual Studio, delete the cache folder {0}, and then try again. ...
- TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have ...
- TF201074: The {0} link between work items {1} and {2} that you are attempting to modify does not exist. It may have been ...
- TF201075: You cannot create a new field using an existing name. Your work item metadata cache may be out of date. Close Visual ...
- TF201075: You cannot create a new field using an existing name. Your work item metadata cache may be out of date. Refresh ...
- TF201076: You cannot create a new field using an existing reference name. Your work item metadata cache may be out of date. ...
- TF201076: You cannot create a new field using an existing reference name. Your work item metadata cache may be out of date. ...
- TF201078: You are trying to import a type of work item that uses the field '{0}'. Your definition of the field includes a ...
- TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' ...
- TF203004: The administrator has set a limit of {0} rows for this operation. Verify the parameters of your operation and try ...
- TF203005: The database does not contain any changesets. The most common cause for this error is database corruption caused ...
- TF203006: Cannot shelve {0}. The item exists in a deleted folder that has a pending undelete change. Include the root folder ...
- TF203007: Cannot create the label because the version controlled item {0} already exists or has been specified more than ...
- TF203013: The path {0} is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try ...
- TF203018: You cannot roll back item {0} because the file contents of the version to which you are rolling back has been destroyed. ...
- TF203021: You cannot simultaneously pend a delete and an edit on item {0} because you have a later version of the item in ...
- TF203022: You cannot provide a workspace or label as the beginning range of a version spec without specifying the /toversion ...
- TF203028: You cannot create a branch at {0} because a branch already exists at {1}. If {1} is not a branch convert it back ...
- TF203029: You cannot update the branch parent to {0} because it is already a child of the branch you are trying to update. ...
- TF203031: You cannot set the branch parent to {0}, because it will cause the branch-nesting to exceed the maximum value of ...
- TF203032: You cannot update the branch parent to {0} because no merge relationship exists between the current branch and ...
- TF203034: The administrator has set a limit of {0} inputs for this operation. Verify the parameters of your operation and ...
- TF203049: One or more pending changes have changed in your workspace during the operation you were attempting. Try your operation ...
- TF203050: Only the first 100 warnings for files that are opened or are not the latest version are included for this unshelve ...
- TF203051: Cannot rollback item {0} because the workspace version of the item is at or older than the version to which you ...
- TF203056: Cannot check in the change to folder / file {0} because its parent folder has a pending rename change. You must ...
- TF203057: Cannot check in the rename change for folder {0} because there are files or folders in this folder with pending ...
- TF203058: Cannot rename {0} to {1} because it will have the same name as the item being added or renamed to {1}. You must ...
- TF203062: Unable to apply label {1} to item {0} because this item has not yet been checked in. Check in this item and then ...
- TF203063: Your files could not be checked in. Try the operation again; if it fails, contact your system administrator for ...
- TF203065: No files could be rolled back to the specified version because you did not provide an itemspec to identify which ...
- TF203066: The rename from {0} to {1} could not be rolled back because you did not provide the source name. To roll back the ...
- TF203067: The rename from {0} to {1} could not be rolled back because you did not provide the target name. To roll back the ...
- TF203068: The operation cannot be completed until you upgrade your client application to the most recent version. If the ...
- TF203069: {0} could not be deleted because that change conflicts with one or more other pending changes to that item. To ...
- TF203071: The operation cannot be completed because the source folder that you specified contains a branch. If you want to ...
- TF203072: A proxy record with the URL that you specified ({0}) could not be added because a proxy record with that URL already ...
- TF203073: The proxy record with the URL that you specified ({0}) could not be deleted because no proxy record with that URL ...
- TF203074: Cannot use the option that you specified to resolve the namespace conflict with item {0} because this item is a ...
- TF203074: Cannot use the option that you specified to resolve the namespace conflict with item {0} because this item is a ...
- TF203075: Cannot complete the rollback operation on {0} because this item is a folder, and the result of rollback operation ...
- TF203076: Cannot complete the rollback operation on {0} because this item is a file, and the result of rollback operation ...
- TF203077: Cannot use the AutoMerge option to resolve the conflict on item {0} because the item does not exist in the current ...
- TF203078: Cannot complete the operation because you specified an incorrect ArtifactKind. To complete this operation, you ...
- TF203093: You attempted to check in one or more items while specifying an invalid check-in date and time stamp. The date ...
- TF203094: You attempted to check in one or more items while specifying an invalid check-in date and time stamp. The date ...
- TF203095: Your attempt to reset the check-in dates in the team project collection failed because the date and time stamp ...
- TF203096: Your attempt to reset the check-in dates in the team project collection failed because one or more of the team ...
- TF203097: You attempted to either reset the check-in dates in a team project collection or to check in one or more items ...
- TF203098: You cannot unshelve a change to {0} because there is a conflict on this item in your workspace. You must first ...
- TF203099: You cannot unshelve a merge change to {0} because a merge change to this item is already pending in your workspace. ...
- TF203100: You cannot unshelve a change to {0} because a deletion of this item is already pending in your workspace. You must ...
- TF203101: You cannot unshelve a deletion of {0} because a change to a child of this item is pending in your workspace. You ...