Visual Studio 2013

  1. The Release dashboard provides an overview of the work on the product backlog. For information on how to use this dashboard, ...
  2. The release path selected must be active. Prior to activate the release template, you must activate the release path or select ...
  3. The release template you are trying to open is currently locked by another user. To modify it, wait for the other user to ...
  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 included in the 'Remote Tools for Visual Studio 2013' installer. The latest version can be downloaded ...
  10. The remote debugger is not correctly installed on the remote computer. Repair your remote debugger installation using 'Add ...
  11. The remote debugger is unable to communicate with Visual Studio, and must abort the remote debugging session. Please restart ...
  12. The remote debugger service was successfully configured. However, the service did not start due to a logon failure. Verify ...
  13. The remote debugger tries to load the 2.0 Common Language Runtime (CLR). This option suppresses the warning that appears ...
  14. The remote debugger was closed while a remote debugging session was active. This remote debugger must abort this session. ...
  15. The remote debugger was unable to initialize Microsoft Windows Web Services (webservices.dll). If the problem continues, ...
  16. The remote debugger was unable to listen on the specified hostname. The format is invalid or is not assigned to this computer. ...
  17. The Remote Debugger was unable to locate a resource dll (vsdebugeng.impl.resources.dll). Please ensure that the complete ...
  18. The remote debugging components are not registered or running on the web server. Ensure the proper version of msvsmon is ...
  19. The remote graphics diagnostics engine failed to open a connection endpoint because the port is in use. Only one diagnostics ...
  20. The remote machine is missing ARM kits policy to enable debugging on that machine. To install ARM kits policy please visit ...
  21. The remote procedure could not be debugged. This usually indicates that debugging has not been enabled on the server. See ...
  22. The rename operation cannot be completed because the designer required to refactor the generated code has not been activated. ...
  23. The rename operation cannot be completed because the document designer is closed. Open the document designer and perform ...
  24. The report cannot be displayed because the trace is corrupt or was collected using a newer version of the Concurrency Visualizer. ...
  25. The report was uploaded, but a warning occurred. The severity of the warning is: {1}. The message is: {2}. The code is: {0}. ...
  26. The representation of this type is hidden by the signature. It must be given an attribute such as ], or to indicate the characteristics ...
  27. The request could not be completed as the communication with the service failed. Check the inner exception for more details. ...
  28. The request failed as the response from the service could not be understood. Try again after few seconds. If the problem ...
  29. The request failed as the response from the service could not be understood. Try again after few seconds. If the problem ...
  30. The request failed as the service identity could not be verified. Try again after few seconds. If the problem persists, contact ...
  31. The request failed as the service identity could not be verified. Try again after few seconds. If the problem persists, contact ...
  32. The request failed because the current user does not have permissions on the account {1}. Verify the permissions and try ...
  33. The request failed because the current user does not have permissions on the account {1}. Verify the permissions and try ...
  34. The request failed because the current user does not have permissions on the account {1}. Verify the permissions and try ...
  35. The request failed because the current user does not have permissions on the account {1}. Verify the permissions and try ...
  36. The request failed due to an internal error on the service. Try again after few seconds. If the problem persists, contact ...
  37. The request failed due to an internal error on the service. Try again after few seconds. If the problem persists, contact ...
  38. The request for the URL '{0}' failed. Ensure that the web site is configured correctly on the web server and is accessible. ...
  39. The request timed out due to lack of response from the service. Check your internet connectivity and try again after few ...
  40. The request timed out due to lack of response from the service. Check your internet connectivity and try again after few ...
  41. The request timed out due to lack of response from the service. Check your internet connectivity and try again after few ...
  42. The request timed out due to lack of response from the service. Check your internet connectivity and try again after few ...
  43. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  44. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  45. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  46. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  47. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  48. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  49. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  50. The request timed out due to lack of response from the service. Try again after few seconds. If the problem persists, contact ...
  51. The requested mapping matches an existing mapping on server path ({0} to {1}) as well as a different mapping on local path ...
  52. The requester of this code review made changes ({0}) to {1}. To add a file-level comment, right-click this link and then ...
  53. The required version of SharePoint Foundation {0} or SharePoint Server {0} is not installed on this system. SharePoint must ...
  54. The reservation for build agent {0} is invalid. The agent workflow might have not been started or already completed with ...
  55. The reset settings operation cannot be completed because no vssettings file has been specified, please specify a valid vssettings ...
  56. The resource dictionary "{0}" cannot be added because it would create a circular reference. The order of references is: {1} ...
  57. The resource dictionary "{0}" cannot be merged into "{1}", since "{1}" contains errors which prevent it from being updated. ...
  58. The resource file is corrupted and cannot be edited; there may be a problem with the resource script. Create the resource ...
  59. The resource file is corrupted, or the editor for this type of file is not available. Create another resource file or install ...
  60. The resource listed below uses this symbol. To change the symbol name or value, click "View Use" and edit the ID for the ...
  61. The resource name or ID specified in reserved by Visual Studio. The reserved names are DESIGNINFO, HWB, and TEXTINCLUDE, ...
  62. The resource script %s was not created using Microsoft Visual Studio. Comments, macros, preprocessor directives, and conditionally ...
  63. The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, ...
  64. The resource will be generated as this type in the strongly-typed resource class. For example, the resource might be generated ...
  65. The response from the request is stored in the file '{0}' with the test results; typically this file can be opened with a ...
  66. The result of methods that return new instances of strings should be assigned to a variable and subsequently used. If the ...
  67. The results file "{0}" already exists. Please specify a different results file or verify the existing file is no longer needed ...
  68. The returned rows appear in the Results pane and the database server continues to retain the result set in its local memory, ...
  69. The right bounds of the substring that needs to be extracted from the script area of the ListView WebPart. For example '\' ...
  70. The right-hand side of an 'instanceof' expression must be of type 'any' or of a type assignable to the 'Function' interface ...
  71. The root folder where the file will be deployed to the SharePoint server. Change the Deployment Type property to select the ...
  72. The root of the caching directory is too long for the Git service to use. Please ensure the entire path length for the caching ...
  73. The rule '{0}' in the rule provider for analyzer '{1}' has an empty rule ID, namespace, or analyzer ID, which are required ...
  74. The rule '{0}' in the rule provider in analyzer '{1}' conflicts with another rule in the rule provider in analyzer '{2}' ...
  75. The rule represents a traditional "for" loop. The context parameter is initialized before the first loop iteration. The loop ...