Visual Studio 2013

  1. The value for this item is stale due to a problem that occurred while evaluating it. Hover your cursor over the refresh button ...
  2. The value for {0} in {1} ({2}) is read-only and could not be updated with the value provided. Please refresh the screen and ...
  3. The value must be a relative path that specifies the location of the file. The path must be relative to the project item's ...
  4. The value must be of type "{0}" or must be the string formed from concatenating the string elements using the Separator string. ...
  5. The value must be of type "{0}", or a string denoting the name of one of the AdmissibleValues, or an integer denoting the ...
  6. The value of Scheduler Timeout "{0}" is invalid. It should be an integer greater than or equal to zero, and zero means infinite. ...
  7. The value of the ExpectedResponseUrl property '{0}' does not equal the actual response URL '{1}'. QueryString parameters ...
  8. The value of the property {2} of the {1} with ID {0} cannot be changed because its properties are locked, either individually ...
  9. The value of this expression may be incorrect. It could not be evaluated because: '%1' Click this button to attempt reevaluation ...
  10. The value of this expression may be incorrect. It could not be evaluated because: '{0}' Click this button to try reevaluation ...
  11. The Value property of one or more StringValueFormat attributes is not specified. Remove these attributes or specify a format ...
  12. The value {0} contains an odd number of double-quote characters. Only even numbers of literal double-quote characters are ...
  13. The value {0} is not valid for the requested by parameter. Valid values include build agent and build controller uniform ...
  14. The values entered do not total 100%. You can choose to accept the entered values or return to the dialog to adjust them. ...
  15. The values for the TFSName and ProjectName elements are not valid. Open the XML file, verify that the values for these elements ...
  16. The variable '%1$ls' already holds a %2$ls: Putting a new resource into this variable may cause the prior value to be lost. ...
  17. The variable '%1' is referenced or declared outside of the selection but used within an anonymous method or a lambda expression. ...
  18. The variable '{0}' is bound in a quotation but is used as part of a spliced expression. This is not permitted since it may ...
  19. The VC++ projects in the solution will be upgraded to use the Microsoft Visual Studio 2013 platform toolset and .NET Framework ...
  20. The vector that defines the direction in which light is cast from a light source in the tangent space of the current pixel. ...
  21. The vector that defines the direction in which light is cast from a light source in world space. You can use this to calculate ...
  22. The vector that extends from the current pixel to the camera in tangent space. You can use this to calculate reflections ...
  23. The vector that extends from the current pixel to the camera in world space. You can use this to calculate reflections in ...
  24. The version of Conman Client running on the device is incompatible with the desktop. Bootstrap the device with desktop compatible ...
  25. The version of Remote Tools for Visual Studio running on '{0}' does not match the version of Visual Studio you are using. ...
  26. The version of the .NET Framework that is installed is not the correct version for this version of . Some features of the ...
  27. The version of the selected solution is higher than the solution version supported by this Visual Studio release. Please ...
  28. The VersionControlServer with which this pending change is associated does not match the VersionControlServer provided when ...
  29. The view above visualizes the execution of threads in the profiled process. Execution segments are sampled. To see a specific ...
  30. The view object "{0}" is not one of the supported types for initializing a DocumentObject. The view must implement either ...
  31. The virtual machine name is used to identify the machine in an environment. This name does not have to match the computer ...
  32. The visibility of the imported elements within the importing Package. If private, the imported elements can be seen only ...
  33. The Visual SourceSafe database folder could not be accessed. Would you like to switch to the Visual SourceSafe Internet plug-in ...
  34. The Visual SourceSafe database folder could not be accessed. Would you like to switch to the Visual SourceSafe LAN plug-in ...
  35. The Visual Studio debugger cannot connect to the remote computer. An RPC policy is enabled on the local computer which prevents ...
  36. The Visual Studio debugger cannot connect to the remote computer. Unable to initiate DCOM communication. Please see Help ...
  37. The Visual Studio debugger cannot establish a DCOM connection to the remote computer. A firewall may be preventing communication ...
  38. The Visual Studio Managed Extensibility Framework Package is not installed as part of Visual Studio. The project system cannot ...
  39. The Visual Studio Remote Debugger (MSVSMON.EXE) has insufficient privileges to debug this process. To debug this process, ...
  40. The Visual Studio Remote Debugger (MSVSMON.EXE) has insufficient privileges to debug this process. To debug this process, ...
  41. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. A firewall may be preventing ...
  42. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. It ...
  43. The Visual Studio Remote Debugging Monitor cannot debug managed code running on the currently installed version of the Microsoft ...
  44. The Visual Studio setup option "Windows Phone 8 SDK" needs to be installed to load this project. To install, choose "Install ...
  45. The Visual Studio Shell Prerequisites requirements to install LocProductName for this system have not been met. Please run ...
  46. The Visual Studio Test Runner is not supported on this version of the server. An alternate test runner has been selected. ...
  47. The visualization is too large and cannot be saved to a file or copied to the clipboard. Remove some branches and try again. ...
  48. The vsglog file was not generated on the latest version of Windows. To get the best diagnostics experience, recapture on ...
  49. The VSP file that you are attempting to switch to is already open with a different filter. Do you want to close the currently ...
  50. The warehouse and Analysis Services databases are offline, but there are reporting jobs still running. Wait until the jobs ...
  51. The warehouse and Analysis Services databases cannot be rebuilt because there are reporting jobs still running. Wait until ...
  52. The warning settings for one or more configurations conflict. Changing this setting will reset the settings in all configurations. ...
  53. The Web Farm Framework v1.1 is not installed. To install Web Farm Framework v1.1 execute one of following commands from the ...
  54. The web page could not be accessed. If the page is refreshing, please wait until the page refreshes and then perform actions ...
  55. The Web project %0 must be converted to the new Web site format. If you continue with this open from source control the project ...
  56. The web project %0 will be treated as uncontrolled because it was converted to the new Web site format. If you want source ...
  57. The Web request '{0}' completed successfully without running the test. This can occur when configuring the Web application ...
  58. The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server. ...
  59. The web server has been locked down and is blocking the DEBUG verb, which is required to enable debugging. Please see Help ...
  60. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the ...
  61. The web server process that was being debugged has been terminated by Internet Information Services (IIS). This can be avoided ...
  62. The web server worker processes exited or debugging was aborted before the debugger was able to complete attaching to the ...
  63. The web services enumeration components are not available. You need to reinstall Visual Studio to add web references to your ...
  64. The web site could not be configured correctly; getting ASP.NET process information failed. Requesting '{0}' returned an ...
  65. The web site could not be configured correctly; getting ASP.NET process information failed. The server may not be running ...
  66. The Web site path '{0}' does not exist. Tests configured to run in ASP.NET Development Server must specify a valid path to ...
  67. The Web site path '{0}' does not exist. Tests configured to run in ASP.NET Development Server must specify a valid path to ...
  68. The Web test '{0}' defines a column for data source table (Data Source: '{1}' Table: '{2}' Column: '{3}' )that is not included ...
  69. The Web Test Recorder browser extension is not properly installed. This prevents the Web Test Recorder from starting automatically. ...
  70. The Web test {0} was stopped because it encountered an excessive number of exceptions while attempting to submit requests ...
  71. The web version of the '{0}' has not been implemented for this release. You may still be able to use Team Web Access to edit ...
  72. The web.config file for the site {0} contains information from a previous run. Replacing it with the backup file ({1}) should ...
  73. The web.config file for the site {0} contains information from a previous run. The web.config file was generated, so deleting ...
  74. The web.config file has been set up with an assemblyPostProcessor different than {0}. Only one assemblyPostProcessor attribute ...
  75. The website metabase contains unexpected information or you do not have permission to access the metabase. You must be a ...