UI Translation

Visual Studio 2012

  1. The workspace name '{0}' exceeds the maximum allowed limit of '{1}' characters. Truncating it to match the maximum limit. ...
  2. The WorkspaceInfo.Folders property is only available for WorkspaceInfo objects with a Location of WorkspaceLocation.Local. ...
  3. The xap file name that you entered is wrong. A file name shouldn't have any of {0} characters. The xap file name has been ...
  4. The XML content in this document cannot be viewed as a graph because it contains unexpected errors. If you Open the XML Editor ...
  5. The XML file for the test artifacts cannot be validated. Verify that the XML schema exists and it contains all the test artifacts. ...
  6. The XML input is invalid or malformed. Check Configuration Servicer Providers section in WM SDK to find out how to use configuration ...
  7. The zip file being created contains a character within the path or file name whose value is greater than 127. The zip file ...
  8. The zoom level to show graph initially as a floating point number where 1 means 100%, or the word "Fit" to fit the graph ...
  9. The _ATL_MIN_CRT preprocessor definition is no longer supported in ATL. The setting 'Minimize CRT Use in ATL' has been removed ...
  10. The _ATL_MIN_CRT preprocessor definition is no longer supported in ATL. The setting ?Minimize CRT Use in ATL? has been removed ...
  11. The {0} 2.0 and {0} 3.5 compilers are no longer supported. Templates will always be compiled with the version 4 compiler ...
  12. The {0} and {1} Work Item fields were filtered out of the available columns list because there are user defined columns already ...
  13. The {0} definitions in the signature and implementation are not compatible because a CLI type representation is being hidden ...
  14. The {0} definitions in the signature and implementation are not compatible because a type representation is being hidden ...
  15. The {0} definitions in the signature and implementation are not compatible because an abbreviation is being hidden by a signature. ...
  16. The {0} definitions in the signature and implementation are not compatible because the abbreviations differ: {1} versus {2} ...
  17. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was present ...
  18. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was required ...
  19. The {0} definitions in the signature and implementation are not compatible because the accessibility specified in the signature ...
  20. The {0} definitions in the signature and implementation are not compatible because the field '{1}' was present in the implementation ...
  21. The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
  22. The {0} definitions in the signature and implementation are not compatible because the field {1} was required by the signature ...
  23. The {0} definitions in the signature and implementation are not compatible because the implementation defines a struct but ...
  24. The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' ...
  25. The {0} definitions in the signature and implementation are not compatible because the implementation is an abstract class ...
  26. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  27. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  28. The {0} definitions in the signature and implementation are not compatible because the implementation type is not sealed ...
  29. The {0} definitions in the signature and implementation are not compatible because the implementation type is sealed but ...
  30. The {0} definitions in the signature and implementation are not compatible because the order of the fields is different in ...
  31. The {0} definitions in the signature and implementation are not compatible because the respective type parameter counts differ ...
  32. The {0} definitions in the signature and implementation are not compatible because the signature declares a {1} while the ...
  33. The {0} definitions in the signature and implementation are not compatible because the signature defines the {1} '{2}' but ...
  34. The {0} definitions in the signature and implementation are not compatible because the signature has an abbreviation while ...
  35. The {0} definitions in the signature and implementation are not compatible because the signature is an abstract class but ...
  36. The {0} definitions in the signature and implementation are not compatible because the signature requires that the type supports ...
  37. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  38. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  39. The {0} deployment slot is occupied on the following hosted service: {1}. To fix the problem you must either delete existing ...
  40. The {0} is a one to zero or one relationship therefore it must be mapped on the key fields and only the key fields of both ...
  41. The {0} name '{1}' contains invalid characters. The name cannot: - contain any of the following characters: / ? : \ " < > ...
  42. The {0}, and {1} Work Item fields were filtered out of the available columns list because there are user defined columns ...
  43. The {0}beginner's guide{1} has a step-by-step walkthrough on how to upload your source code, setup a build, and start managing ...
  44. Then, if you want to reestablish the result set, you can rerun the query or view. Do you want to prolong your work with the ...
  45. There already exists a parameter with the name '{0}'. Parameter names must be unique within a query and amongst the parameters ...
  46. There already exists an item with the same name under source control. If you continue with the add, this item will automatically ...
  47. There appears to be a discrepancy between the solution's source control information about some project(s) and the information ...
  48. There are additional errors that have been truncated from the log. These errors can be viewed in the event log for the application-tier ...
  49. There are conflicting XmlnsCompatibleWithAttributes in assemblies '{0}' and '{1}' for OldNamespace '{2}'. Change the attributes ...
  50. There are critical errors in the application definition metadata. Those errors must be fixed before the project can be loaded ...
  51. There are currently bindings for this context parameter. Do you want to replace these bindings with the parameter's current ...
  52. There are currently no launch targets for this performance session. To add a launch target, right click on the Targets folder ...
  53. There are currently no library shares configured for the following project: {0}. Contact your system administrator and ask ...
  54. There are currently {0} work items selected. A maximum of {1} work items can be opened at once. Please select {1} or fewer ...
  55. There are errors in the error list which may prevent Refresh Windows app from completing successfully or your application ...
  56. There are errors in the error list which may prevent your application from functioning correctly. Would you like to start ...
  57. There are files locked in the extension you are trying to update / uninstall. Please close any {0}solutions that may be referencing ...
  58. There are more old test run results than the limit defined in execution options. If you continue older results will be deleted. ...
  59. There are more than one intrinsic data sources in the project, including '{0}'. Remove invalid data sources from the project. ...
  60. There are multiple applications named '{0}'. Specify the PackageFullName of the application to be profiled using /package. ...
  61. There are multiple configurations that have diagnostic data adapter type '{0}' or Uri '{1}'. Duplicate configurations will ...
  62. There are multiple environments with the specified name in the project. Use the 'TeamProjectHostGroup' or 'TeamProjectLibraryShare' ...
  63. There are multiple test environments found with display name {0}. Use the fully-qualified name of the environment, as displayed ...
  64. There are multiple users with the same display name {0} and at least one of them does not have read permissions to some of ...
  65. There are no abstract members defined in base class {0} or the members have already been overridden in the current class. ...
  66. There are no accessible team project collections in this Team Foundation Server. Contact your Team Foundation Server administrator. ...
  67. There are no accessible team projects in this Team Project Collection. Contact your Team Foundation Server administrator. ...
  68. There are no areas selected for your team. You must select at least one area to enable features such as your product backlog ...
  69. There are no configured extension galleries. Galleries can be configured on the Extensions and Updates page in the Options ...
  70. There are no data objects in your project that can be previewed. The Data Preview dialog box requires configured DataAdapters ...
  71. There are no hosts associated with host group path '{0}'. Use the SCVMM Administrator Console to add at least one host to ...
  72. There are no license grants that apply to this user, so the user is receiving access according to the system's default CAL ...
  73. There are no solution or project files in this location. Please select a different location. To open a Web site or for more ...
  74. There are no steps to run in the active deployment configuration. Specify the list of steps to run in the Project Properties. ...
  75. There are no stored virtual machines available for this team project. You can {0} a virtual machine into the team project ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)