Visual Studio 2013

  1. The code file for the coded UI test has been added to your test project. To proceed, you can select from the options below. ...
  2. The code for {0} is not ready to be read yet. In some cases, saving all files and generating again will fix this issue. Additional ...
  3. The code in assembly '{0}' makes uses of quotation literals. Static linking may not include components that make use of quotation ...
  4. The code index database exists but is not in usable state. Please repair/delete the database and try again. Code index connection ...
  5. The code index database exists but is not of the expected version. The database cannot be recovered automatically as a custom ...
  6. The code requires a running document table, but none is available, indicating we are not running under the Visual Studio ...
  7. The code review was updated on the server. There were merge conflicts on fields that prevented a successful merge. Please ...
  8. The Coded UI Test is running in Single Thread Apartment (STA) mode of COM. In this mode, all the playback calls should happen ...
  9. The Coded UITest cannot be run as a 64 bit process. You must change your test settings in the Hosts tab to run your test ...
  10. The collection database you have selected is part of a SQL AlwaysOn group or database mirror, which requires servicing to ...
  11. The collection pre-creation job starts creating new collections when the number of available pre-created collections is less ...
  12. The collection process (VsStandardCollector.exe) unexpectedly aborted, possibly due to a crash. The profiling session will ...
  13. The collection property '{0}' is not editable because it is part of a many-to-many association. All many-to-many associations ...
  14. The collection property '{0}' is not editable because there isn't a navigation property on the other side of the association. ...
  15. The collection you have selected is part of a SQL AlwaysOn group or database mirror, which must be serviced in the FULL recovery ...
  16. The collectionName or collectionId parameter must be specified with the jobs command. Type "TfsConfig help jobs" for command ...
  17. The column for property {0}.{1} cannot be added because the attribute UserVisibleProperty has the same id '{2}' as property ...
  18. The column headers represent the State values, and the row headers represent the following field: {0}. Each intersection ...
  19. The command '%1' cannot be bound because the command '%2' is already bound to the same keyboard shortcut, %3, within the ...
  20. The command '{0}' is invalid. Expecting the following format: tfs server uri . In case of spaces the expressions should be ...
  21. The command '{0}' is invalid. Expecting the following format: tfs server uri ]. In case of spaces the expressions should ...
  22. The command cannot be completed because the file '{0}' cannot be changed. If the file is under source control, check the ...
  23. The command ChangeServerId should only be run against a set of Team Foundation Server databases that have no application ...
  24. The command object you are using requires named parameters (such as '@param') rather than '?'. Check the description of the ...
  25. The command requires an active tool window, Source Control Explorer or Solution Explorer, or one of the options, /fromsce ...
  26. The command text "{0}" was executed on connection "{1}", building an OdbcDataReader using one of the CommandBehavior values. ...
  27. The command text "{0}" was executed on connection "{1}", building an OleDbDataReader using one of the CommandBehavior values. ...
  28. The command text is invalid. To call a stored procedure through ODBC managed provider the following syntax should be used: ...
  29. The command you are attempting cannot be completed because the file '%1' that must be modified cannot be changed. If the ...
  30. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  31. The command you are attempting cannot be completed because the file(s) '{0}' that must be modified cannot be changed. If ...
  32. The command {0} was not recognized. At the command prompt, type "TestControllerConfig.exe Help" to get a list of available ...
  33. The command {0} was not recognized. At the command prompt, type "VSTestConfig.exe Help" to get a list of available commands. ...
  34. The command-line option '-cliroot' has been deprecated. Use an explicit reference to a specific copy of mscorlib.dll instead. ...
  35. The command-line option '{0}' has been deprecated. HTML document generation is now part of the F# Power Pack, via the tool ...
  36. The commit can no longer be amended. It is either no longer the tip of the current branch or it has been pushed to a remote ...
  37. The Common Language Runtime cannot stop at this exception. Common causes include: incorrect COM interop marshalling and memory ...
  38. The Common Language Runtime cannot stop at this exception. Common causes include: incorrect COM interop marshalling, and ...
  39. The communication timeout was reached while cleaning up test execution. To change the timeout, specify the "TestCommunicationTimeout" ...
  40. The communication timeout was reached while setting up test execution. To change the timeout, specify the "TestCommunicationTimeout" ...
  41. The component set contains a C# website with no code directory. Search is not supported on the referenced assemblies of such ...
  42. The components listed above must be installed in the same language version as the operating system. You must manually install ...
  43. The compound word '{0}' in assembly name {1} exists as a discrete term. If your usage is intended to be single word, case ...
  44. The compound word '{0}' in member name {1} exists as a discrete term. If your usage is intended to be single word, case it ...
  45. The compound word '{0}' in namespace name '{1}' exists as a discrete term. If your usage is intended to be single word, case ...
  46. The compound word '{0}' in type name {1} exists as a discrete term. If your usage is intended to be single word, case it ...
  47. The computer '{0}' has more than one display. By default, only the screen from the primary display will be recorded. Run ...
  48. The computer needs to be restarted before setup can continue. Restart the computer and setup will resume when you next log ...
  49. The Concurrency Visualizer cannot start because ETW collection is currently in progress. See http://go.microsoft.com/fwlink/?LinkID=217390 ...
  50. The Concurrency Visualizer cannot store trace files under the specified directory: {0} Specify a valid directory and try ...
  51. The Concurrency Visualizer does not have sufficient permissions to write to the specified directory: {0} Specify a valid ...
  52. The Concurrency Visualizer SDK does not support the selected project type. Only Visual C#, Visual Basic, and Visual C++ projects ...
  53. The condition for a breakpoint failed to execute. The condition was '{0}'. The error returned was '{1}'. Click OK to stop ...
  54. The Conditional attribute is not valid on '%1!ls!' because it is a constructor, destructor, operator, or explicit interface ...
  55. The conditional expression will be executed against the target type of the style if must return a boolean. If it returns ...
  56. The configuration could not be loaded from the registry: {0} Do you want to delete the current configuration and reconfigure ...
  57. The configuration editor cannot be loaded. Make sure that the configuration editor for the following diagnostic data adapter ...
  58. The configuration of the selected diagnostic data adapter as specified on the agents is invalid. Please check the default ...
  59. The configuration option to delete ETL files after analysis is selected. This setting will ignored for system-wide traces. ...
  60. The configuration service host cannot stop because a running process is preventing it from stopping. The process name is ...
  61. The configuration to build for the solution. Access the Property Pages dialog box for the solution to modify the solution's ...
  62. The connection is not correctly authenticated or the authentication type is not supported. You may only switch your user ...
  63. The connection string appears to contain sensitive data (for example, a password) and it will be stored in test source code ...
  64. The connection string for the database has not been set. To store your results in a database for post-run analysis, set the ...
  65. The connection string in the generated code may contain plain text passwords and/or other sensitive information. Please review ...
  66. The connection string used by the selected objects contains sensitive information that will be saved in the application configuration ...
  67. The connection to the database failed for the following reason: %1 No server references can be added at this time, but you ...
  68. The connection to the Web server for page '{0}' was lost. {1}. Check that the Web server is still running and visible on ...
  69. The connection you have created does not work with the current data adapter because it uses a diffent managed data provider ...
  70. The connection you selected uses a local data file that is not in the current project. Would you like to copy the file to ...
  71. The constant 0 can be converted to a null pointer constant by a standard conversion, static_cast, reinterpret_cast, C-style ...
  72. The constant 0 can be converted to a null pointer-to-member constant by a standard conversion, static_cast, reinterpret_cast, ...
  73. The constituent members of {0} appear to represent flags that can be combined rather than discrete values. If this is correct, ...
  74. the constraints for generic parameter '%$S' of function '%$D'%$Nmust match the constraints for generic parameter '%$S' of ...
  75. The constraints for type parameter '%1!ls!' of method '%2!ls!' must match the constraints for type parameter '%3!ls!' of ...