UI Translation

Visual Studio 2013

  1. The window search cannot be created. The specified parent control type is not supported. Supported parent types include FrameworkElement, ...
  2. The Windows Azure SDK for .NET enables developers to build, debug, deploy, and manage scalable applications and services ...
  3. The Windows Firewall on this computer is currently blocking remote debugging. Remote debugging requires that the remote debugging ...
  4. The Windows Firewall on this machine is currently blocking remote debugging. Remote debugging requires that the debugger ...
  5. The Windows Firewall on this machine will be configured to allow remote debugging. The remote debugger (msvsmon.exe) must ...
  6. The Windows Installer service cannot update one or more protected Windows files. {SFP Error: 2]. List of protected files: ...
  7. The Windows Installer service cannot update the protected Windows file 2]. {Package version: 3], OS Protected version: 4], ...
  8. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  9. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows ...
  10. The Windows Installer service is unavailable. Another application may be running setup. Finish any installations in progress, ...
  11. The Windows Software Development Kit (SDK) required by the XAML Designer was not correctly installed. Consider repairing ...
  12. The Windows Web Services API installation completed, but a reboot is required before the API is available. This computer ...
  13. The WmAppManifest.xml is not part of the project. All Windows Phone projects must have this manifest file. Please either ...
  14. The work associated with this review is not currently active. Activate it now](Switch to the task associated with this code ...
  15. The work item cannot be created because the current session or result is not valid. Close the current activity and launch ...
  16. The work item could not be mapped because an error occurred when attempting to update the link to the parent work item. You ...
  17. The work item could not be moved to the sprint or backlog because an error occurred when attempting to update the iteration ...
  18. The work item could not be updated. An error occurred while attempting to update the required fields of the work item. The ...
  19. The work item has been modified on Team Foundation Server in the middle of publish process. Refresh the document, re-apply ...
  20. The work item store is not configured correctly. You must have at least one work item type in the category with reference ...
  21. The Work Item Tracking database refers to build Uris that cannot be resolved. These builds may have been deleted. Work items ...
  22. The work items linked to this model element are in these servers: {0}. To see the linked work items, connect Team Explorer ...
  23. The workflow instance accepted a stop request but did not complete within {0}. This may indicate an AsyncCodeActivity is ...
  24. The workflow instance did not accept a stop request within {0}. This typically indicates that a CodeActivity is blocking ...
  25. The working folder(s) of the existing workspace '{0}' cannot be unmapped to create a temporary workspace for uploading the ...
  26. The worksheet you are trying to change is protected and therefore read-only. To remove protection, click Excel in the designer, ...
  27. The workspace name '{0}' exceeds the maximum allowed limit of '{1}' characters. Truncating it to match the maximum limit. ...
  28. The WorkspaceInfo.Folders property is only available for WorkspaceInfo objects with a Location of WorkspaceLocation.Local. ...
  29. 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 ...
  30. The XML content in this document cannot be viewed as a graph because it contains unexpected errors. If you Open the XML Editor ...
  31. The XML file for the test artifacts cannot be validated. Verify that the XML schema exists and it contains all the test artifacts. ...
  32. The XML input is invalid or malformed. Check Configuration Servicer Providers section in WM SDK to find out how to use configuration ...
  33. The zip file being created contains a character within the path or file name whose value is greater than 127. The zip file ...
  34. The zoom level to show graph initially as a floating point number where 1 means 100%, or the word "Fit" to fit the graph ...
  35. The _ATL_MIN_CRT preprocessor definition is no longer supported in ATL. The setting 'Minimize CRT Use in ATL' has been removed ...
  36. The _ATL_MIN_CRT preprocessor definition is no longer supported in ATL. The setting ?Minimize CRT Use in ATL? has been removed ...
  37. The {0} 2.0 and {0} 3.5 compilers are no longer supported. Templates will always be compiled with the version 4 compiler ...
  38. The {0} and {1} Work Item fields were filtered out of the available columns list because there are user defined columns already ...
  39. The {0} definitions in the signature and implementation are not compatible because a CLI type representation is being hidden ...
  40. The {0} definitions in the signature and implementation are not compatible because a type representation is being hidden ...
  41. The {0} definitions in the signature and implementation are not compatible because an abbreviation is being hidden by a signature. ...
  42. The {0} definitions in the signature and implementation are not compatible because the abbreviations differ: {1} versus {2} ...
  43. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was present ...
  44. The {0} definitions in the signature and implementation are not compatible because the abstract member '{1}' was required ...
  45. The {0} definitions in the signature and implementation are not compatible because the accessibility specified in the signature ...
  46. The {0} definitions in the signature and implementation are not compatible because the field '{1}' was present in the implementation ...
  47. The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
  48. The {0} definitions in the signature and implementation are not compatible because the field {1} was required by the signature ...
  49. The {0} definitions in the signature and implementation are not compatible because the implementation defines a struct but ...
  50. The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' ...
  51. The {0} definitions in the signature and implementation are not compatible because the implementation is an abstract class ...
  52. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  53. The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
  54. The {0} definitions in the signature and implementation are not compatible because the implementation type is not sealed ...
  55. The {0} definitions in the signature and implementation are not compatible because the implementation type is sealed but ...
  56. The {0} definitions in the signature and implementation are not compatible because the order of the fields is different in ...
  57. The {0} definitions in the signature and implementation are not compatible because the respective type parameter counts differ ...
  58. The {0} definitions in the signature and implementation are not compatible because the signature declares a {1} while the ...
  59. The {0} definitions in the signature and implementation are not compatible because the signature defines the {1} '{2}' but ...
  60. The {0} definitions in the signature and implementation are not compatible because the signature has an abbreviation while ...
  61. The {0} definitions in the signature and implementation are not compatible because the signature is an abstract class but ...
  62. The {0} definitions in the signature and implementation are not compatible because the signature requires that the type supports ...
  63. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  64. The {0} definitions in the signature and implementation are not compatible because the signature says this type may use nulls ...
  65. The {0} deployment slot is occupied on the following hosted service: {1}. To fix the problem you must either delete existing ...
  66. 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 ...
  67. The {0} is configured to track the Created/Modified state but the following Created/Modified properties are missing or misconfigured: ...
  68. The {0} name '{1}' contains invalid characters. The name cannot: - contain any of the following characters: / ? : \ " < > ...
  69. The {0}, and {1} Work Item fields were filtered out of the available columns list because there are user defined columns ...
  70. 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 ...
  71. 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 ...
  72. There already exists a parameter with the name '{0}'. Parameter names must be unique within a query and amongst the parameters ...
  73. There already exists an item with the same name under source control. If you continue with the add, this item will automatically ...
  74. There appears to be a discrepancy between the solution's source control information about some project(s) and the information ...
  75. There are additional errors that have been truncated from the log. These errors can be viewed in the event log for the application-tier ...
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)