Visual Studio 2013

  1. Request could not be processed because a required configuration setting indicating the client application that should be ...
  2. Request for cross-domain policy at '{0}' timed out: Web services might not be accessible. For more details please contact ...
  3. Request for UI feedback permission "{1}" refused: CONFLICT DETECTED .{0}Conflicting permission: {2}{0}Requesting recognizer ...
  4. Request stakeholders to provide feedback on an application that your team has built or plans to build. See the Privacy Statement ...
  5. Request to url: {1} failed with the following exception: {0}{2}{0} If the problem persists, contact Team Foundation Service ...
  6. Request to url: {1} failed with the following exception: {0}{2}{0} If the problem persists, contact Visual Studio Online ...
  7. Requests queued by users or triggered by the system will be added to the queue but will not start unless the build administrator ...
  8. Required assemblies 'WindowsBase', 'PresentationCore', and 'PresentationFramework' are missing from the target framework. ...
  9. Required Boolean. If TRUE, the field must have value assigned to it before an item that is created using this content type ...
  10. Required if reference element is specified for an Assembly reference. This tag supports both simple text and strong name ...
  11. Required Text. Specifies the content type name. The value can be a reference to a resource in the format $Resources:String. ...
  12. Required Text. Specifies the field ID of the column that this FieldRef element references. The field ID is the string representation ...
  13. Required Text. The displayed name for the column. Maximum length is 255 characters. The value of this attribute is used as ...
  14. Required Text. The name of a column. This is the internal name of a column and is guaranteed never to change for the lifetime ...
  15. Required Text. The name of a field. This is the internal name of a field and is guaranteed never to change for the lifetime ...
  16. Required. Association name of the list or site workflow to start (WF3.5 based 2010-style workflow). HINT: To see List association ...
  17. Required. Collection of Strings. Valid formats include: user (full email address, full display name, user name in claims ...
  18. Required. Content Type of the task that will be created in the tasks list. NOTE: You must also add the selected task content ...
  19. Required. Default outcome of the task if it does not complete successfully. NOTE: You must first set the ContentTypeId and ...
  20. Required. Field in the specified Content Type that will be the task's Outcome field. HINT: to use default, specify "TaskOutcome". ...
  21. Required. Login name or ID of the SP user or group to assign to the task. HINT: example login name in claims format, for ...
  22. Required. Login name(s) or IDs of the SP user or group to assign to the task. HINT: example login name in claims format, ...
  23. Required. Message to write to the current workflow history list. NOTE: Requires a history list to be assiciated to this workflow. ...
  24. Required. Specify either FieldValue or FieldValueDynamicValue, not both. Use this for complex value types that require DynamicValue. ...
  25. Required. Specify either FieldValue or FieldValueDynamicValue, not both. Use this for simple value types such as Boolean, ...
  26. Requirement Status by Config: Helps the team identify gaps in test coverage for each test configuration for each requirement. ...
  27. Requirement Status: Helps the team identify gaps in test coverage for each requirement. This report requires that team members ...
  28. Rescan Solution Interval : A 'Rescan Solution Now' job will be scheduled every 'value' minutes. The value must be between ...
  29. Reset test to include shared step modifications in this test and other pending tests. Resetting will discard any currently ...
  30. Resolve #using References : Specifies one or more directories (separate directory names with a semicolon) to be searched ...
  31. Resolves conflicts between changed items in your workspace and the latest or destination versions of items on the server. ...
  32. Resource '{0}' has a name that is not recommended and that may cause compilation errors in your code. Please choose another ...
  33. Resource could not be found. A resource with the name '{0}' provided in '{1}' for the diagnostic data adapter of type '{2}' ...
  34. Resource dll DiagnosticsHubMsg.dll failed to load. If the problem continues, run setup to install or repair the Diagnostics ...
  35. Resource names can not be null or empty. The resource name provided for '{0}' on the diagnostic data adapter of type '{1}' ...
  36. Resources generated by pre-release versions of the .NET Framework might contain incorrect or incomplete type references. ...
  37. Resources larger than {0} KB are not supported. The following resource(s) are too large to be added and will be ignored: ...
  38. Restart the Visual Studio Team Foundation Job Agent and the Microsoft Team Foundation Server Application Pool on all machines ...
  39. Restart this application under different credentials Saves the current changes and then restarts the application. You will ...
  40. Restart under different credentials Saves the current changes and then restarts %s. You will be prompted to change your user ...
  41. Restart Visual Studio and run the New Team Project Wizard again. If the problem persists, contact your Team Foundation Server ...
  42. Restart your debug session after trying one or more of the following steps: 1. Specify the path to '%s' in Symbol Settings ...
  43. Restarting the debugging session using "{0}" has failed. If this is a temporary issue, you can try to start your debugging ...
  44. Restarting the Team Project Collection {0} job on {1}. You can view the status of this job using the Team Foundation Server ...
  45. Restores items that were previously deleted. tf undelete /noget /lock:(none|checkin|checkout) /recursive itemspec[;deletionID ...
  46. Restores shelved file revisions, check-in notes, comments, and work item associations to the current workspace or removes ...
  47. Restores the environment to a snapshot. This activity can be used only with virtual environments managed by System Center ...
  48. Result files for this test run were expected but not found. Any additional details such as code coverage or test-specific ...
  49. Results from agent '{0}' were not received in time to be included in the overall results for a sampling interval. To avoid ...
  50. Resume keyword Specifies where execution should continue after an error is handled, or resumes execution after an error-handling ...
  51. Resumes the macro recorder from the paused state so code is written to the recording macro (Not to be used from within a ...
  52. rethrows a caught exception and specifies it explicitly as an argument. Use 'throw' without an argument instead, in order ...
  53. Retrieves a read-only copy of a file from Team Foundation Server to the local workspace and creates folders on disk to contain ...
  54. Retrieves a specific version of a file to a temporary folder on your computer and displays it. tf view /collection:TeamProjectCollectionUrl ...
  55. Retrieves recent error messages that occurred during synchronization of Team Foundation Server and Project Server. For each ...
  56. Retrieves toolbar customization information and notifies the toolbar's parent window of any changes being made to the toolbar ...
  57. Return statement Returns execution to the code that called the Function, Sub, Get, Set, or Operator procedure. Return -or- ...
  58. return types for 'begin' and 'end' functions used in a range-based 'for' statement must be the same ('begin' return type ...
  59. Return' statements in this Async method cannot return a value since the return type of the function is 'Task'. Consider changing ...
  60. Returning '%1$ls' from failed function call at line '%2$ls'. A successful path through the function is returning a variable ...
  61. Returning uninitialized memory '%1$ls'. A successful path through the function does not set the named _Out_ parameter. %2$ls ...
  62. Returns a collection of breakpoints that represent this breakpoint's children. If the breakpoint has no children then nothing ...
  63. Returns a value that indicates whether the key identifier for this instance can be resolved to the specified key identifier. ...
  64. Returns properties of an SP principal (Principal represents a user or a group in SharePoint that can be assigned permissions). ...
  65. Returns properties of an SP Principal (Principal represents a user or a group in SharePoint that can be assigned permissions). ...
  66. Returns the collection in which this bound breakpoint resides, essentially providing the set of children owned by a pending ...
  67. Reverse engineer C++ type is not supported. Some DGML node(s) will be skipped during the process. Please see warnings for ...
  68. Reverse engineer process encountered memory issue. Please split up namespaces/types in smaller sections to reverse engineer ...
  69. Reverting this activity will lose any changes you've made, and get the latest details from the server. Are you sure you want ...
  70. Review declarative security for {0} and its callers for potential vulnerabilities. The following call stack might expose ...
  71. Review declarative security for {0} and its callers for potential vulnerabilities. This method is accessible from outside ...
  72. Review field names which, by convention, appear to indicate they are instance or static but, in fact, are not. This rule ...
  73. Review parameters in non-virtual methods that are not used in the method body to ensure no correctness exists around failure ...
  74. Review the following for a possible security vulnerability: In {0}, the class member {1} is being passed to a {2} constructor. ...
  75. Review the following for a possible security vulnerability: In {0}, the return value of a call to {1} is being passed to ...