Visual Studio 2012

  1. The changes that you selected will invalidate one or more signatures that are applied to this document. Are you sure you ...
  2. The changes you made to links and attachments have not been saved to the Team Foundation Server. Do you want to continue ...
  3. The changesets you are tracking include a large number of items. You should specify a path to a smaller number of items to ...
  4. The character encoding for the file %s has changed. Your source control provider may have problems managing files with this ...
  5. The character set tag in this file defines a code page which is not valid or not installed on your system. You can install ...
  6. The character was incomplete at stream offset {0:d}. The file labeled '{1}' might be in a different encoding than {2}, or ...
  7. The chart below combines the average queue time and run time for jobs; you can also view how many jobs were run at each hour. ...
  8. The chart below describes the job queue; it provides the counts for each queue type. The possible values are: InProgress, ...
  9. The chart below displays the number of different result types over the time period. Click on any of the result types to display ...
  10. The chart below displays the number of times a job has run combined with the number of result types for that particular job. ...
  11. The chart below displays total amount of run time this particular job has taken over the time period. Click on any of the ...
  12. The checkout has failed or been cancelled. Any subsequent edits made to the file must be saved to a different file using ...
  13. The checkout has failed or been cancelled. Any subsequent edits made to the file must be saved to a different file using ...
  14. The child test '{0}' with id '{1}' of test '{2}' with id '{3}' could not be found. Make sure that child test container exists. ...
  15. The chosen buffer size is not large enough to support overhead calculations. Try using fewer counters or larger buffers. ...
  16. The chosen file has incorrect file type {0}. Please choose a file whose type matches {1}, or change the logical name ({2}) ...
  17. The class cannot be exposed to VBA code because the document does not contain a VBA project, or because you do not have permission ...
  18. The class cannot be exposed to VBA code because the GuidAttribute declaration is missing or corrupt in the following file: ...
  19. The class cannot be exposed to VBA code because the version number specified by the AssemblyVersionAttribute is not valid ...
  20. The Class Designer allows you to visualize and work with types in your code. Create new types by dragging items from the ...
  21. The Class Designer allows you to visualize types in your code. Visualize existing types by dragging items from the {0} or ...
  22. The client certificates configuration was affected by machine-wide settings. To inspect and modify machine-wide settings, ...
  23. The client is not configured to use cookies. Support for cookies is required by the client when using Windows authentication ...
  24. The Client Libraries feature of the Silverlight {0} SDK is required before creating a Silverlight project. Re-run the Silverlight ...
  25. The clipboard cannot be accessed. Close this dialog box and attempt the Clipboard operation again. If this failure occurs ...
  26. The ClockController.Seek method was called using TimeSeekOrigin.Duration as the seekOrigin parameter for a Clock that has ...
  27. The ClockController.Seek method was called with arguments that describe a seek destination that seeks a child with Slip but ...
  28. The ClockController.Seek method was called with arguments that describe a seek destination with a negative value. The seek ...
  29. The Code Analysis policy requires rules not included in the Express version of Visual Studio. Double-click this message for ...
  30. The Code Analysis settings for one or more projects are not compatible with Code Analysis policy. Double-click this message ...
  31. The Code Analysis window does not support the platform toolset version of one or more projects. See the Error List for results ...
  32. The code could not be generated because the cursor in the source code file is not located within a method. Place the cursor ...
  33. The Code Coverage Analysis Service could not analyze the code coverage data for build {0} ({1}/{2}). This is frequently caused ...
  34. The code coverage data could not be written to the BuildCoverage or RunCoverage table in the Team Foundation Build database ...
  35. The code coverage data could not be written to the BuildCoverage or RunCoverage table in the Team Foundation Build database: ...
  36. The code coverage results to update could not be read from the BuildCoverage, RunCoverage, or Platforms_Flavors table in ...
  37. The code file for the coded UI test has been added to your test project. To generate code for this test, you can select from ...
  38. 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 ...
  39. The code in assembly '{0}' makes uses of quotation literals. Static linking may not include components that make use of quotation ...
  40. The code index database exists but is not in usable state. Please repair/delete the database and try again. Code index connection ...
  41. The code index database exists but is not of the expected version. The database cannot be recovered automatically as a custom ...
  42. The code requires a running document table, but none is available, indicating we are not running under the Visual Studio ...
  43. The code review was updated on the server. There were merge conflicts on fields that prevented a successful merge. Please ...
  44. The Coded UI Test is running in Single Thread Apartment (STA) mode of COM. In this mode, all the playback calls should happen ...
  45. 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 ...
  46. The collection pre-creation job starts creating new collections when the number of available pre-created collections is less ...
  47. The collection process (VsEtwCollector.exe) unexpectedly aborted, possibly due to a crash. The profiling session will now ...
  48. The collection property '{0}' is not editable because it is part of a many-to-many association. All many-to-many associations ...
  49. The collection property '{0}' is not editable because there isn't a navigation property on the other side of the association. ...
  50. The collectionName or collectionId parameter must be specified with the jobs command. Type "TfsConfig help jobs" for command ...
  51. The CollectionView that originates this CurrentChanging event is in a state that does not allow the event to be canceled. ...
  52. The column '{0}' is of a user-defined type, but has a collation which differs from the default database collation. Because ...
  53. The column definition from this {0} function cannot be verified, and the operations involved with it might not be understood ...
  54. The column for property {0}.{1} cannot be added because the attribute UserVisibleProperty has the same id '{2}' as property ...
  55. The column headers represent the State values, and the row headers represent the following field: {0}. Each intersection ...
  56. The column {0} on table {1} must be added, but the column does not allow NULL values. You must bind the default {2} to it. ...
  57. The column {0} on table {1} must be added, but the column has no default value and does not allow NULL values. If the table ...
  58. The column {0} on table {1} must be changed from NULL to NOT NULL. If the table contains data, the ALTER script may not work. ...
  59. The command '%1' cannot be bound because the command '%2' is already bound to the same keyboard shortcut, %3, within the ...
  60. The command cannot be completed because the file '{0}' cannot be changed. If the file is under source control, check the ...
  61. The command ChangeServerId should only be run against a set of Team Foundation Server databases that have no application ...
  62. The command object you are using requires named parameters (such as '@param') rather than '?'. Check the description of the ...
  63. The command requires an active tool window, Source Control Explorer or Solution Explorer, or one of the options, /fromsce ...
  64. The command text "{0}" was executed on connection "{1}", building an OdbcDataReader using one of the CommandBehavior values. ...
  65. The command text "{0}" was executed on connection "{1}", building an OleDbDataReader using one of the CommandBehavior values. ...
  66. The command text is invalid. To call a stored procedure through ODBC managed provider the following syntax should be used: ...
  67. The command you are attempting cannot be completed because the file '%1' that must be modified cannot be changed. If the ...
  68. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  69. The command you are attempting cannot be completed because the file(s) '{0}' that must be modified cannot be changed. If ...
  70. The command {0} was not recognized. At the command prompt, type "TestControllerConfig.exe Help" to get a list of available ...
  71. The command {0} was not recognized. At the command prompt, type "VSTestConfig.exe Help" to get a list of available commands. ...
  72. The command-line option '-cliroot' has been deprecated. Use an explicit reference to a specific copy of mscorlib.dll instead. ...
  73. The command-line option '{0}' has been deprecated. HTML document generation is now part of the F# Power Pack, via the tool ...
  74. The Common Language Runtime cannot stop at this exception. Common causes include: incorrect COM interop marshalling and memory ...
  75. The Common Language Runtime cannot stop at this exception. Common causes include: incorrect COM interop marshalling, and ...