Visual Studio 2010

  1. The database that you specified cannot be used. The database exists, but it is not a warehouse database for Team Foundation ...
  2. The database that you specified does not exist. A new database will be created and populated for use with Team Foundation ...
  3. The database you entered is already in use by another Team Project Collection. You must enter a database that is not in use. ...
  4. The database you selected is new or does not contain any objects. Click Finish to create an empty dataset. Once database ...
  5. The database you specified cannot be used. The database exists, but its schema is not valid for use with Team Foundation ...
  6. The DatabaseSchemaProviderFamily extension {0} could not be loaded because there is already another DatabaseSchemaProviderFamily ...
  7. The DataGrid's selected items collection no longer supports INotifyCollectionChanged. This means we don't get events on multi-select. ...
  8. The DataPoint {2} in the {0} {1}' has the name "{3}". DataValue names cannot be null and must be unique within the DataValues ...
  9. The DataPoints in the {0} {1}' has an invalid set of {2} items. {2} names must be unique within the {2} collection for the ...
  10. The DataProviderServices extension {0} could not be loaded because there is already another DataProviderServices extension ...
  11. The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data ...
  12. The DataSet Project property in {0} must be set to a project that targets the same version of the .NET Framework as the current ...
  13. The DataSet Project property must be set to a project that targets the same version of the .NET Framework as the current ...
  14. The DataSetFile attribute is missing or empty in {0}. Datasets that contain non-Null DataSetProject values require a valid ...
  15. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  16. The DataSourceID of the ReportDataSource '{0}' of the ReportViewer '{1}' must be the ID of a control of type IDataSource. ...
  17. The DATA_COMPRESSION option was specified more than once for the target, or for at least one of its partitions if the target ...
  18. The date range '|' is not valid because it is not in the form ' and '. Type the range again in the correct form, such as ...
  19. The date/time is converted to the RFC1123 standard format. It follows the custom pattern 'ddd, dd MMMM yyyy HH:mm:ss G\MT'. ...
  20. The date/time is converted to the universal full format. Pattern is always the same regardless of culture or format provider. ...
  21. The date/time is converted to the universal sortable format. Pattern is always the same regardless of culture or format provider. ...
  22. The date/time that the blob was last modified. Any operation that modifies the blob, including an update of the blob's metadata ...
  23. The DB Command "{0}" is not completely configured. To resolve this problem, set the CommandText and Connection properties ...
  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 cannot connect to the remote computer. This may be because the remote computer does not exist or a firewall ...
  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 on %s cannot connect to this computer. The Windows Firewall is preventing communication via DCOM to this computer. ...
  32. The debugger option "Enable the exception assistant" is turned on. This option may cause instability in Web Application projects ...
  33. The debugger was unable to automatically select an appropriate type of code. Please manually specify the type(s) of code ...
  34. The debugger was unable to terminate one or more processes: %1 The debugger may be unstable now. It is recommended that you ...
  35. The declaration form 'let . and .' for non-recursive bindings is not used in F# code. Consider using a sequence of 'let' ...
  36. The declarations in this file will be placed in an implicit module '{0}' based on the file name '{1}'. However this is not ...
  37. The declared type parameters for this type extension do not match the declared type parameters on the original type '{0}' ...
  38. The default connect string for the samples should work without modification if you have SQL Server Express installed on your ...
  39. The default connect string for the samples should work without modification if you have Sql Server Express installed on your ...
  40. The default document type is created by the New Document toolbar button and the CTRL+N keyboard shortcut. A different default ...
  41. The default format for documents in the 2007 Microsoft Office system. Choose this format for all documents unless your solution ...
  42. The default OnDrawAdvanced prepares a normalized device context for drawing, then calls your control class's OnDraw method. ...
  43. The default script that is generated at deployment time results in dropping the existing table (column) and adding a new ...
  44. The default site location for new team projects created in this team project collection. You should use a site collection ...
  45. The default transport lets you select processes on this computer or a remote computer running the Microsoft Visual Studio ...
  46. The default value of the common path if it is not already defined in the hosting process. Normally the hosting process will ...
  47. The default value specified for parameter '%1!ls!' will have no effect because it applies to a member that is used in contexts ...
  48. The default Web access mode for this project is set to file share, but the project folder at '%1' cannot be opened with the ...
  49. The default Web access mode for this project is set to FrontPage, but the project folder at '%1' cannot be opened with FrontPage. ...
  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 demand or link demand on {0} will not prevent the struct from being instantiated but it will only be initialized with ...
  52. The dependency or hierarchy link types in this Project file is no longer available on the server. You can either restore ...
  53. The deployment item you have selected, '{0}', is not in the current solution folder. If these test settings are used on a ...
  54. The deployment manifest could not be downloaded because a connection to the network could not be established. Ensure that ...
  55. The Deployment Package Wizard will now create the Windows Installer Package. Deploy the policy through Group Policy or Systems ...
  56. The deployment script was generated, but was not deployed. You can change the deploy action on the Deploy tab of the project ...
  57. The deployment scripts and optional arguments will be run in the order that is shown in the following list. You can add new ...
  58. The deployment type "{0}" of project output reference "{1}" in Project Item "{2}" is not compatible with a Feature in a Sandboxed ...
  59. The deployment type "{0}" of project output reference "{1}" in Project Item "{2}" is not compatible with a Package in a Sandboxed ...
  60. The DeploymentContributor {0} does not match the contributor registered at build time; the {1} does not match. {2} was expected, ...
  61. The DeploymentContributor {0} that was present during build is missing. Because the deployment contributor is missing, it ...
  62. The design time assembly '{0}' you have compiled against is not the same version used by Visual Studio. Recompile your design ...
  63. The designer cannot process the code at line {0}, please see the Task List for details. The code within the method '{1}' ...
  64. The designer cannot process the code at line {0}: {1} The code within the method '{2}' is generated by the designer and should ...
  65. The designer contains multiple BindingSources that are bound to the same data source. Which BindingSource would you like ...
  66. The designer does not support an application URI in an assembly other than the application. Change '{0}' to be relative to ...
  67. The designer does not support loading dictionaries that mix '{0}' items without a key and other items in the same collection. ...
  68. The designer has fixed inconsistent type names in a partial class. The partial class name '{1}' has been changed to '{0}'. ...
  69. The designer loader class {0} either does not inherit from DesignerLoader or does not implement IVSMDDesignerLoader. Both ...
  70. The designer requires a markup text model in order to display. The project you are currently using does not offer a text ...
  71. The destination site ignores case. The following pairs of names will conflict: %1!.300s! No files were copied. Name all files ...
  72. The detach operation disconnects all data related to this Team Project Collection from the Team Foundation Server. The physical ...
  73. The detailed format is not valid when listing all workspaces on this computer. To use the detailed format, please specify ...
  74. The developer centers are your gateways to tutorials, samples, videos, blogs, forums, and other resources that can help you ...
  75. The Development Fabric must be run elevated. Please restart Visual Studio in elevated administrator mode in order to run ...