Visual Studio 2010

  1. The Client Libraries feature of the Silverlight {0} SDK is required before creating a Silverlight project. Re-run the Silverlight ...
  2. The client program has made a request that the server did not recognize. You may have specified an invalid proxy server. ...
  3. The ClockController.Seek method was called using TimeSeekOrigin.Duration as the seekOrigin parameter for a Clock that has ...
  4. The ClockController.Seek method was called with arguments that describe a seek destination that seeks a child with Slip but ...
  5. The ClockController.Seek method was called with arguments that describe a seek destination with a negative value. The seek ...
  6. The Code Analysis settings for one or more projects are not compatible with Code Analysis policy. Double-click this message ...
  7. The code change might have been moved or deleted since the last time the project was built. Some code changes do not have ...
  8. The code could not be generated because the cursor in the source code file is not located within a method. Place the cursor ...
  9. The Code Coverage Analysis Service could not analyze the code coverage data for build {0} ({1}/{2}). This is frequently caused ...
  10. The code coverage data could not be written to the BuildCoverage or RunCoverage table in the Team Foundation Build database ...
  11. The code coverage data could not be written to the BuildCoverage or RunCoverage table in the Team Foundation Build database: ...
  12. The code coverage results to update could not be read from the BuildCoverage, RunCoverage, or Platforms_Flavors table in ...
  13. 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 ...
  14. 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 ...
  15. The Code Group Properties dialog box allows you to edit this code group's name, description, membership condition, and permission ...
  16. The code in assembly '{0}' makes uses of quotation literals. Static linking may not include components that make use of quotation ...
  17. The code or macros in this file do not match the digital signature. This mismatch was most likely caused by one of the following: ...
  18. The code or macros in this file do not match the digital signature. This mismatch was most likely caused by the file being ...
  19. The code requires a running document table, but none is available, indicating we are not running under the Visual Studio ...
  20. The code-behind class '%1' is not found in code-behind file '%2', instead it is found in '%3'. So the 'CodeFile' attribute ...
  21. The Coded UI Test is running in Single Thread Apartment (STA) mode of COM. In this mode, all the playback calls should happen ...
  22. 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 ...
  23. The collation used for this column in the database, as specified in the schema. The collation determines the languages that ...
  24. The collectionName or collectionId parameter must be specified with the jobs command. Type "TfsConfig help jobs" for command ...
  25. The CollectionView that originates this CurrentChanging event is in a state that does not allow the event to be canceled. ...
  26. The column '{0}' is of a user-defined type, but has a collation which differs from the default database collation. Because ...
  27. The column definition from this {0} function cannot be verified, and the operations involved with it might not be understood ...
  28. The column for property {0}.{1} cannot be added because the attribute UserVisibleProperty has the same id '{2}' as property ...
  29. The column {0} is not part of a foreign key constraint. Ensure that the foreign key generator is not used on non-foreign ...
  30. 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. ...
  31. 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 ...
  32. 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. ...
  33. The comma separated style shows the titles for items in the list with all the other field values separated by commas underneath ...
  34. The command '%1' cannot be bound because the command '%2' is already bound to the same keyboard shortcut, %3, within the ...
  35. The command cannot be completed because the file '{0}' cannot be changed. If the file is under source control, check the ...
  36. The command ChangeServerId should only be run against a set of Team Foundation Server databases that have no application ...
  37. The command generation failed for the following tables. Tables with failed command generation will not sync correctly and ...
  38. The command object you are using requires named parameters (such as '@param') rather than '?' for parameterized queries. ...
  39. The command object you are using requires named parameters (such as '@param') rather than '?'. Check the description of the ...
  40. The command set for this design surface is not available. Either the design surface has not been loaded or the view hasn't ...
  41. The command text "{0}" was executed on connection "{1}", building an OdbcDataReader using one of the CommandBehavior values. ...
  42. The command text "{0}" was executed on connection "{1}", building an OleDbDataReader using one of the CommandBehavior values. ...
  43. The command text is invalid. To call a stored procedure through ODBC managed provider the following syntax should be used: ...
  44. The command you are attempting cannot be completed because the file '%0' is under source code control and is not checked ...
  45. The command you are attempting cannot be completed because the file '%1' that must be modified cannot be changed. If the ...
  46. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  47. The command you are attempting cannot be completed because the file '{0}' that must be modified cannot be changed. If the ...
  48. The command {0} was not recognized. At the command prompt, type "TestControllerConfig.exe Help" to get a list of available ...
  49. The command {0} was not recognized. At the command prompt, type "VSTestConfig.exe Help" to get a list of available commands. ...
  50. The command-line option '-cliroot' has been deprecated. Use an explicit reference to a specific copy of mscorlib.dll instead. ...
  51. The command-line option '{0}' has been deprecated. HTML document generation is now part of the F# Power Pack, via the tool ...
  52. The common language runtime uses code access security to control applications' access to protected resources. Each application's ...
  53. The common language runtime's code access security system determines an assembly's permissions to access protected resources. ...
  54. The communication timeout was reached while cleaning up test execution. To change the timeout, specify the "TestCommunicationTimeout" ...
  55. The communication timeout was reached while setting up test execution. To change the timeout, specify the "TestCommunicationTimeout" ...
  56. The comparison results may be incorrect for table/view {0} because the source and target databases have different base types ...
  57. The comparison results may be incorrect for table/view {0} because the source and target databases have different collations ...
  58. The component set contains a C# website with no code directory. Search is not supported on the referenced assemblies of such ...
  59. The compound word '{0}' in assembly name {1} exists as a discrete term. If your usage is intended to be single word, case ...
  60. The compound word '{0}' in member name {1} exists as a discrete term. If your usage is intended to be single word, case it ...
  61. The compound word '{0}' in namespace name '{1}' exists as a discrete term. If your usage is intended to be single word, case ...
  62. The compound word '{0}' in type name {1} exists as a discrete term. If your usage is intended to be single word, case it ...
  63. The Conditional attribute is not valid on '%1!ls!' because it is a constructor, destructor, operator, or explicit interface ...
  64. The conditional expression will be executed against the target type of the style if must return a boolean. If it returns ...
  65. The configuration could not be loaded from the registry: {0} Do you want to delete the current configuration and reconfigure ...
  66. The configuration editor cannot be loaded. Make sure that the configuration editor for the following diagnostic data adapter ...
  67. The configuration of the selected diagnostic data adapter as specified on the agents is invalid. Please check the default ...
  68. The configuration parameter SharePointIntegrated is set to True but Share Point Object Model cannot be loaded. The error ...
  69. The configuration service host cannot stop because a running process is preventing it from stopping. The process name is ...
  70. The configuration to build for the solution. Access the Property Pages dialog box for the solution to modify the solution's ...
  71. The Configure an Assembly wizard allows you to add or remove permissions from this permission set. This wizard also allows ...
  72. The connection information retrieved contains an incompatible query type, or was created using an incompatible query format. ...
  73. The connection property in the Application Settings file is missing or incorrect. The connection string from the {0} file ...
  74. The connection property in the web.config file is missing or incorrect. The connection string from the {0} file has been ...
  75. The connection string appears to contain sensitive data (for example, a password) and it will be stored in test source code ...