Visual Studio 2013

  1. The Data Source value in the connection sting specifies an instance of SQL Server that is not installed. To resolve this ...
  2. The data source was not disposed before the application was terminated. Consider calling IVsUISimpleDataSource.Close() when ...
  3. The Data Sources window encountered an error while trying to display the data source. Verify the data source is correct, ...
  4. The data warehouse has detected data conflicts for the following work item fields. The conflicts occur because there are ...
  5. The database connection information could not be found. Please verify that the TFS database is running and accessible and ...
  6. The database file that you are attempting to connect to is not compatible with the current instance of SQL Server. To continue, ...
  7. The database for the following team project collection is not reachable: {0}. The server that hosts the database is: {1}. ...
  8. The database that you specified cannot be used. The database exists, but it is not a warehouse database for Team Foundation ...
  9. The database that you specified does not exist. A new database will be created and populated for use with Team Foundation ...
  10. The database you entered is already in use by another Team Project Collection. You must enter a database that is not in use. ...
  11. The database you have selected is part of a SQL AlwaysOn group or database mirror, which must be upgraded in the FULL recovery ...
  12. The database you have selected is part of a SQL AlwaysOn group or database mirror, which require upgrade to be performed ...
  13. The database you selected is new or does not contain any objects. Click Finish to create an empty dataset. Once database ...
  14. The database you specified cannot be used. The database exists, but its schema is not valid for use with Team Foundation ...
  15. The DataContext type cannot be determined because the Type property specified in the DesignData binding either cannot be ...
  16. The DataContext type cannot be determined because the Type property specified in the DesignData binding either cannot be ...
  17. The DataGrid's selected items collection no longer supports INotifyCollectionChanged. This means we don't get events on multi-select. ...
  18. The DataSet Project property in {0} must be set to a project that targets the same version of the .NET Framework as the current ...
  19. The DataSet Project property must be set to a project that targets the same version of the .NET Framework as the current ...
  20. The DataSetFile attribute is missing or empty in {0}. Datasets that contain non-Null DataSetProject values require a valid ...
  21. The DB Command "{0}" is not completely configured. To resolve this problem, set the CommandText and Connection properties ...
  22. The debug driver for the selected Debugging Accelerator Type is not installed on the target machine. For more information, ...
  23. The debug driver for the selected Debugging Accelerator Type is not installed on the target machine. For more information, ...
  24. The debug mode is Program, but there is no program specified. Please specify a program using the project's Debug property ...
  25. The debug source files settings for the active solution indicate that the debugger will not ask the user to find the file: ...
  26. The debugger attempted to call a function within the debugged process but this function did not complete in time. The debugger ...
  27. The debugger attempted to call a function within the debugged process but this function did not complete in time. The state ...
  28. The debugger does not support debugging managed and native code at the same time on the platform of the target computer/device. ...
  29. The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. ...
  30. The debugger is still attaching to the process or the process is not currently executing the type of code selected for debugging. ...
  31. The debugger was unable to automatically select an appropriate type of code. Please manually specify the type(s) of code ...
  32. The debugger was unable to communicate with its worker process (msvsmon.exe) due to a protocol compatibility error. Ensure ...
  33. The debugger was unable to find the registration for the target application. If the problem persists, try uninstalling and ...
  34. The debugger was unable to install Windows Web Services API because an installer for the current operating system version ...
  35. The debugger was unable to install Windows Web Services API. Downloading the update installer failed. Please ensure that ...
  36. The debugger was unable to terminate one or more processes: %1 The debugger may be unstable now. It is recommended that you ...
  37. The debugger will use symbols from this location which is not trusted for automatic downloads: {0} To use this path, click ...
  38. The declaration form 'let . and .' for non-recursive bindings is not used in F# code. Consider using a sequence of 'let' ...
  39. The declarations in this file will be placed in an implicit module '{0}' based on the file name '{1}'. However this is not ...
  40. The declared type parameters for this type extension do not match the declared type parameters on the original type '{0}' ...
  41. The default code index database exists but is not in a usable state. An attempt to automatically recover the database failed. ...
  42. The default drop location for this build {0} is not cloaked. This path will be retrieved and labeled for every build. This ...
  43. The default format for documents in the 2007 Microsoft Office system. Choose this format for all documents unless your solution ...
  44. The default OnDrawAdvanced prepares a normalized device context for drawing, then calls your control class's OnDraw method. ...
  45. The default site location for new team projects created in this team project collection. You should use a site collection ...
  46. The default transport lets you select processes on this computer or a remote computer running the Microsoft Visual Studio ...
  47. The default value of the common path if it is not already defined in the hosting process. Normally the hosting process will ...
  48. The default value specified for parameter '%1!ls!' will have no effect because it applies to a member that is used in contexts ...
  49. The default view that was created by following modeling adapter does not inherit either directly or indirectly from StandardVSModelingDiagramView: ...
  50. The default, zero-initializing constructor of a struct type may only be used if all the fields of the struct type admit default ...
  51. The DefaultLanguage element specified in the app manifest is invalid. It must be one of the values supported by the Windows ...
  52. The demand or link demand on {0} will not prevent the struct from being instantiated but it will only be initialized with ...
  53. The dependency or hierarchy link types in this Project file is no longer available on the server. You can either restore ...
  54. The deployer for server '{0} (local IP Address: {1})' is not valid. Please verify the server configuration. If the Server ...
  55. The deployer is pending an upgrade from version {0} to version {1}. If this takes more than a few minutes, please contact ...
  56. The Deployer user ({0}) does not have access to the crypto store. On the server where the deployment agent is installed, ...
  57. The deployment for release template '{0}' has not been completed successfully. Check the releases history for more details. ...
  58. The deployment has not completed in the time allowed ({0} minutes) to indicate a successful build. You can change this setting ...
  59. The deployment has not completed in the time allowed ({0} minutes) to indicate a successful build. You can change this setting ...
  60. The deployment item you have selected, '{0}', is not in the current solution folder. If these test settings are used on a ...
  61. The deployment task did not complete in the specified time. The specified timeout can be changed by editing the build definition. ...
  62. The deployment type "{0}" of project output reference "{1}" in Project Item "{2}" is not compatible with a Feature in a Sandboxed ...
  63. The deployment type "{0}" of project output reference "{1}" in Project Item "{2}" is not compatible with a Package in a Sandboxed ...
  64. The depth of the current pixel in view space, as determined by interpolating between the depth attributes of nearby vertices. ...
  65. The depth of the current pixel, expressed in normalized device coordinates. The result has a value in the range of 0, 1]. ...
  66. The design time assembly '{0}' you have compiled against is not the same version used by . Recompile your design time assemblies ...
  67. The designer contains multiple BindingSources that are bound to the same data source. Which BindingSource would you like ...
  68. The designer does not support an application URI in an assembly other than the application. Change '{0}' to be relative to ...
  69. The designer requires a markup text model in order to display. The project you are currently using does not offer a text ...
  70. The destination directory ({0}) specified for moving content contains files. A non-existing or empty directory must be specified. ...
  71. The destination directory you specified for moving content already exists. The existing permissions for this directory will ...
  72. The destination directory you specified for moving content contains files. Please specify a non-existing or empty directory ...
  73. The destination project "{0}" does not have requirement workitem category. Ensure that there is a requirement workitem in ...
  74. The destination project "{0}" does not have test case workitem category. Ensure that there is a test case workitem in target ...
  75. The detach operation disconnects all data related to this Team Project Collection from the Team Foundation Server. The physical ...