Visual Studio 2010

  1. The binary files (in _vti_bin) need updating. After installing, check permissions using SharePoint Designer. Installing Windows ...
  2. The bind operation will ignore file differences. Your files may be replaced silently by their server versions on future source ...
  3. The bind operation will scan all your files to detect differences (This may take several minutes to complete). These files ...
  4. The binding information for project %1 could not be retrieved from its source control provider. This project may have been ...
  5. The binding information for this solution could not be retrieved from its source control provider. This solution may have ...
  6. The BITS service is not running. This service is required to download content. Please start the service or contact your system ...
  7. The bottom part of the view offers profile reports for all the non-hidden threads in the currently visible time range: 'Execution' ...
  8. The BOUNDING_BOX parameter of the CREATE SPATIAL INDEX statement is incompletely defined. If the parameter has more than ...
  9. The browser will try to open the build log file. The operation may not succeed due to this browser's security settings. The ...
  10. The browser will try to open the following location. However, the operation may not succeed due to this browser's security ...
  11. The browsing database in this directory is open by another instance of Visual Studio and cannot be reopened. User %1 on %2 ...
  12. The buffer pointed to by the lpstrFile member of the OPENFILENAME structure is too small for the filename specified by the ...
  13. The bug field mapping cannot be loaded from the following file {0}. Verify that the path and the content of the file are ...
  14. The bug field mapping has been modified by another user or session. You must reload the bug field mapping and update it again. ...
  15. The bugfieldmapping command provides the ability to import or export the XML file that maps auto generated bug fields to ...
  16. The Bugs dashboard gives you an overview of the team's progress toward finding and fixing bugs. For information on how to ...
  17. The Bugs dashboard gives you an overview of the team's progress toward finding and fixing bugs. For information on how to ...
  18. The build associated with this IntelliTrace log file has published symbol files to "{0}". This location will be searched ...
  19. The build associated with this IntelliTrace log file no longer exists. You may have to enter the symbol path for this debugging ...
  20. The build associated with this IntelliTrace log file was not configured to publish symbols to a symbol server. You may have ...
  21. The build cannot start while code metrics calculation is in progress. Do you want to cancel? Click Yes to cancel code metrics ...
  22. The build controller associated with this environment is no longer available. You can clear this option or choose another ...
  23. The Build dashboard helps you monitor and measure how builds are progressing. For information on how to use this dashboard ...
  24. The Build dashboard helps you monitor and measure how builds are progressing. For information on how to use this dashboard ...
  25. The build definition {0} must be configured for Gated Check-in to support submitting changes to source control on a successful ...
  26. The build is queued on the following build controller, but that build controller is not configured for workflow: {0}. Queue ...
  27. The build outputs for this private build will not be copied to the drop location because the PrivateDropLocation is not set. ...
  28. The build process failed because all the worksheets in the workbook you are using in this solution are protected. Turn off ...
  29. The build process failed because the document you are using in this solution is protected. Turn off document protection and ...
  30. The build service could not read the Lab Management configuration. Therefore, it could not configure the build service host. ...
  31. The build service encountered an error when it started the configuration thread. Exception type: {0}. Exception message: ...
  32. The build service encountered an error when it updated the build service host name to the computer name: {0}. Exception type: ...
  33. The build service encountered an error while it read the registry for the status of the operating system customization. Exception ...
  34. The build service encountered an error while it updated the registry node with the following information: Key name: {0}; ...
  35. The build service encountered an error while reading the registry node with the following key name: {0}. Exception type: ...
  36. The build service encountered the following error while reading the configuration passed to it by Team Foundation Server: ...
  37. The build service has stopped because the account it runs under does not have the necessary Administrator permissions on ...
  38. The build service ignored the service account provided by Lab Management to connect to the Team Foundation Server application-tier ...
  39. The build service is unable to connect to the following Team Foundation Server application-tier: {0}. Exception type: {1}. ...
  40. The build service is using the same credentials under which it is running to connect to the Team Foundation Server application-tier. ...
  41. The build service is using the service account provided by Lab Management to connect to the Team Foundation Server application-tier. ...
  42. The build service will stop. If this machine is not part of a virtual environment managed by Visual Studio Lab Management, ...
  43. The build type {0} has been upgraded to a build definition without configuring a build controller. You must configure a build ...
  44. The Burndown dashboard displays critical information to help you track progress toward completing an iteration. For information ...
  45. The byref-typed variable '{0}' is used in an invalid way. Byrefs cannot be captured by closures or passed to inner functions. ...
  46. The C/C++ compiler default settings have been modified to be more compliant with ISO Standard C++. Included in those changes ...
  47. The C/C++ compiler switch /Og has been deprecated and has been removed from your project settings. It is recommended that ...
  48. The cache state of one or more tables has been changed. These DataTables will be recreated, overwriting any customizations. ...
  49. The Cached attribute on the following member is in error because the member is not public, static, read-only, or is a parameterized ...
  50. The CachedDataManifest passed to the AppDomainManager could not be loaded because its format is not valid. The XML error ...
  51. The call cannot be completed. Your instant messaging application may not be configured properly or your corporate policy ...
  52. The call to method '%1!ls!' needs to be dynamically dispatched, but cannot be because it is part of a base access expression. ...
  53. The cell formatting table with id: MSCellFormattingTableID="%1" has been customized, and as a result Visual Web Developer ...
  54. The certificate used for signing is invalid at this time. It is most likely expired. The VBA project will not be signed. ...
  55. The certificate with thumbprint {0} could not be used for client authentication. The current user may not have permission ...
  56. The changed value in this cell was not recognized as valid. .Net Framework Data Type: {0} Error Message: {1} Type a value ...
  57. The changes that you selected will invalidate one or more signatures that are applied to this document. Are you sure you ...
  58. The changes you just made to security policy might prevent the .NET Framework Configuration tool from running the next time ...
  59. The changes you made to links and attachments have not been saved to the Team Foundation Server. Do you want to continue ...
  60. The character encoding for the file %s has changed. Your source control provider may have problems managing files with this ...
  61. The character set tag in this file defines a code page which is not valid or not installed on your system. You can install ...
  62. The character was incomplete at stream offset {0:d}. The file labeled '{1}' might be in a different encoding than {2}, or ...
  63. The chart series {0} is missing and cannot be deserialized. You can use Chart.CallbackStateContent='All' to preserve all ...
  64. The checkout has failed or been cancelled. Any subsequent edits made to the file must be saved to a different file using ...
  65. The checkout has failed or been cancelled. Any subsequent edits made to the file must be saved to a different file using ...
  66. The child test '{0}' with id '{1}' of test '{2}' with id '{3}' could not be found. Make sure that child test container exists. ...
  67. The chosen buffer size is not large enough to support overhead calculations. Try using fewer counters or larger buffers. ...
  68. The class cannot be exposed to VBA code because the document does not contain a VBA project, or because you do not have permission ...
  69. The class cannot be exposed to VBA code because the GuidAttribute declaration is missing or corrupt in the following file: ...
  70. The class cannot be exposed to VBA code because the version number specified by the AssemblyVersionAttribute is not valid ...
  71. The Class Designer allows you to visualize and work with types in your code. Create new types by dragging items from the ...
  72. The Class Designer allows you to visualize types in your code. Visualize existing types by dragging items from the {0} or ...
  73. The class file '%1' specified as the codebehind for '%2' could not be loaded. Make sure that the codebehind attribute in ...
  74. The cld-settings file required by the system is missing or corrupted. Please delete your local content ({0}), uninstall and ...
  75. The client certificates configuration was affected by machine-wide settings. To inspect and modify machine-wide settings, ...