Visual Studio 2012

  1. The registration of the app package required by the designer took too long to complete and was canceled. Reload the designer ...
  2. The relative path of the file in the SharePoint server. The fully qualified path for the file is created by concatenating ...
  3. The Release dashboard provides an overview of the work on the product backlog. For information on how to use this dashboard, ...
  4. The remainder of the page is one large FlipView that displays details for one item at a time, allowing the user to flip through ...
  5. The remote computer does not have a CLR version which is compatible with the remote debugging components. To install a compatible ...
  6. The remote debugger can be run as either a Windows service or a Windows application. Running the remote debugger as a service ...
  7. The Remote Debugger cannot be started as an Administrator on Microsoft Windows RT. Restart the remote debugger with normal ...
  8. The remote debugger has encountered a serious internal error, and must abort the remote debugging session. Please restart ...
  9. The remote debugger is not correctly installed on the remote computer. Repair your remote debugger installation using 'Add ...
  10. The remote debugger is unable to communicate with Visual Studio, and must abort the remote debugging session. Please restart ...
  11. The remote debugger service was successfully configured. However, the service did not start due to a logon failure. Verify ...
  12. The remote debugger tries to load the 2.0 Common Language Runtime (CLR). This option suppresses the warning that appears ...
  13. The remote debugger was closed while a remote debugging session was active. This remote debugger must abort this session. ...
  14. The remote debugger was unable to initialize Microsoft Windows Web Services (webservices.dll). If the problem continues, ...
  15. The remote debugger was unable to listen on the specified hostname. The format is invalid or is not assigned to this computer. ...
  16. The Remote Debugger was unable to locate a resource dll (vsdebugeng.impl.resources.dll). Please ensure that the complete ...
  17. The remote debugging components are not registered or running on the web server. Ensure the proper version of msvsmon is ...
  18. The remote procedure could not be debugged. This usually indicates that debugging has not been enabled on the server. See ...
  19. The rename operation cannot be completed because the designer required to refactor the generated code has not been activated. ...
  20. The rename operation cannot be completed because the document designer is closed. Open the document designer and perform ...
  21. The report cannot be displayed because the trace is corrupt or was collected using a newer version of the Concurrency Visualizer. ...
  22. The report was uploaded, but a warning occurred. The severity of the warning is: {1}. The message is: {2}. The code is: {0}. ...
  23. The representation of this type is hidden by the signature. It must be given an attribute such as ], or to indicate the characteristics ...
  24. The request for the URL '{0}' failed. Ensure that the web site is configured correctly on the web server and is accessible. ...
  25. The requested mapping matches an existing mapping on server path ({0} to {1}) as well as a different mapping on local path ...
  26. The requester of this code review made changes ({0}) to {1}. To add a file-level comment, right-click this link and then ...
  27. The required pattern for URI containing ";component" is "AssemblyName;Vxxxx;PublicKey;component", where Vxxxx is the assembly ...
  28. The reservation for build agent {0} is invalid. The agent workflow might have not been started or already completed with ...
  29. The reset settings operation cannot be completed because no vssettings file has been specified, please specify a valid vssettings ...
  30. The resource dictionary "{0}" cannot be added because it would create a circular reference. The order of references is: {1} ...
  31. The resource dictionary "{0}" cannot be merged into "{1}", since "{1}" contains errors which prevent it from being updated. ...
  32. The resource file is corrupted and cannot be edited; there may be a problem with the resource script. Create the resource ...
  33. The resource file is corrupted, or the editor for this type of file is not available. Create another resource file or install ...
  34. The resource listed below uses this symbol. To change the symbol name or value, click "View Use" and edit the ID for the ...
  35. The resource name or ID specified in reserved by Visual Studio. The reserved names are DESIGNINFO, HWB, and TEXTINCLUDE, ...
  36. The resource script %s was not created using Microsoft Visual Studio. Comments, macros, preprocessor directives, and conditionally ...
  37. The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, ...
  38. The resource will be generated as this type in the strongly-typed resource class. For example, the resource might be generated ...
  39. The resources in deletion batch {0} cannot be modified. The deletion batch has already had a job queued or run against it. ...
  40. The response from the request is stored in the file '{0}' with the test results; typically this file can be opened with a ...
  41. The result of methods that return new instances of strings should be assigned to a variable and subsequently used. If the ...
  42. The results file "{0}" already exists. Please specify a different results file or verify the existing file is no longer needed ...
  43. The returned rows appear in the Results pane and the database server continues to retain the result set in its local memory, ...
  44. The reverse engineering operation cannot continue because an error occurred while attempting to verify your permissions in ...
  45. The reverse engineering operation cannot continue because an error occurred while attempting to verify your permissions on ...
  46. The reverse engineering operation cannot continue because you do not have View Any Definition permission on the server '{0}'. ...
  47. The reverse engineering operation cannot continue because you do not have View Definition permission on the '{0}' database. ...
  48. The reverse engineering operation cannot continue because you have been denied View Definition permission on at least one ...
  49. The reverse engineering operation cannot continue because you have been denied View Definition permission on at least one ...
  50. The right bounds of the substring that needs to be extracted from the script area of the ListView WebPart. For example '\' ...
  51. The root folder where the file will be deployed to the SharePoint server. Change the Deployment Type property to select the ...
  52. The root of a Template content section cannot contain an element of type '{0}'. Only FrameworkElement and FrameworkContentElement ...
  53. The rule '{0}' in the rule provider for analyzer '{1}' has an empty rule ID, namespace, or analyzer ID, which are required ...
  54. The rule '{0}' in the rule provider in analyzer '{1}' conflicts with another rule in the rule provider in analyzer '{2}' ...
  55. The rule represents a traditional "for" loop. The context parameter is initialized before the first loop iteration. The loop ...
  56. The rule set file "{0}" is not mapped in the workspace. Edit the workspace to include a mapping for this file and run Code ...
  57. The RuleReferenceHolder does not have a rule reference object. Every RuleReferenceHolders is required to have a rule reference ...
  58. The sample directory already exists. When a sample is created, it must be placed within a new folder of the same name. Choose ...
  59. The save location does not exist on your machine. You will not be able to save a file or open the save location. Please choose ...
  60. The schedule for Full backup task and Differential backup task is the same. The Differential backup task will be scheduled ...
  61. The schema of data returned by your new command could not be retrieved. Schema of table "{0}" was not changed and might not ...
  62. The schema of data returned by your new command could not be retrieved. Schema of table "{0}" was not changed and might not ...
  63. The schema of the data returned by query '{0}' is different than schema returned by main query of the table. Query '{0}' ...
  64. The scope of the label you are creating contains a label or labels with the same name. Do you want to preserve their version ...
  65. The script contains syntax that is not supported by the version of SQL Server that is associated with the database project. ...
  66. The SDK manifest contains registration information for the .winmd file {0}, but there is more than one file with the same ...
  67. The search control does not have options or filters and does not persist most recently searched strings, thus it has no popup. ...
  68. The search provider '{0}' has the category shortcut '{1}' starting with an invalid character. This provider will be ignored. ...
  69. The search provider '{0}' has the category shortcut null, empty or containing whitespace characters. This provider will be ...
  70. The security configuration of this computer is incompatible with certain features used by this application. For more information, ...
  71. The security debugging option is set but it requires the Visual Studio hosting process which is unavailable in this debugging ...
  72. The Security Identity Cleanup Job finished successfully. {0} identities were removed. {1} identities were added. {2} identites ...
  73. The SecurityPermission must be included in your application with the Execute flag set or your application will not run. Mark ...
  74. The SecurityPermission must be included in your application with the Execute flag set or your application will not run. Mark ...
  75. The SecurityPermission must be included in your application with the Execute flag set or your application will not run. The ...