Visual Studio 2012

  1. The version of the .NET Framework that is installed is not the correct version for this version of Visual Studio. Some features ...
  2. The version of the Microsoft SQL Server Compact database that you are adding to the project is not supported by the target ...
  3. The version of the Microsoft SQL Server Compact database that you selected is not supported by the current project. The database ...
  4. The version of the Microsoft SQL Server Compact database that you selected is not supported by the target .NET Framework ...
  5. The version of the selected solution is higher than the solution version supported by this Visual Studio release. Please ...
  6. The VersionControlServer with which this pending change is associated does not match the VersionControlServer provided when ...
  7. The view above visualizes the execution of threads in the profiled process. Execution segments are sampled. To see a specific ...
  8. The view object "{0}" is not one of the supported types for initializing a DocumentObject. The view must implement either ...
  9. The virtual machine name is used to identify the machine in an environment. This name does not have to match the computer ...
  10. The visibility of the imported elements within the importing Package. If private, the imported elements can be seen only ...
  11. The Visual SourceSafe (VSS) upgrade tool allows you to upgrade your existing VSS repositories to Team Foundation Server. ...
  12. The Visual SourceSafe database folder could not be accessed. Would you like to switch to the Visual SourceSafe Internet plug-in ...
  13. The Visual SourceSafe database folder could not be accessed. Would you like to switch to the Visual SourceSafe LAN plug-in ...
  14. The Visual Studio debugger cannot connect to the remote computer. An RPC policy is enabled on the local computer which prevents ...
  15. The Visual Studio debugger cannot connect to the remote computer. Unable to initiate DCOM communication. Please see Help ...
  16. The Visual Studio debugger cannot establish a DCOM connection to the remote computer. A firewall may be preventing communication ...
  17. The Visual Studio Managed Extensibility Framework Package is not installed as part of Visual Studio. The project system cannot ...
  18. The Visual Studio Remote Debugger (MSVSMON.EXE) has insufficient privileges to debug this process. To debug this process, ...
  19. The Visual Studio Remote Debugger (MSVSMON.EXE) has insufficient privileges to debug this process. To debug this process, ...
  20. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. A firewall may be preventing ...
  21. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. It ...
  22. The Visual Studio Remote Debugging Monitor cannot debug managed code running on the currently installed version of the Microsoft ...
  23. The Visual Studio Shell Prerequisites requirements to install LocProductName for this system have not been met. Please run ...
  24. The Visual Studio Test Runner is not supported on this version of the server. An alternate test runner has been selected. ...
  25. The visualization is too large and cannot be saved to a file or copied to the clipboard. Remove some branches and try again. ...
  26. The VSP file that you are attempting to switch to is already open with a different filter. Do you want to close the currently ...
  27. The warehouse and Analysis Services databases are offline, but there are reporting jobs still running. Wait until the jobs ...
  28. The warehouse and Analysis Services databases cannot be rebuilt because there are reporting jobs still running. Wait until ...
  29. The warning settings for one or more configurations conflict. Changing this setting will reset the settings in all configurations. ...
  30. The web page could not be accessed. If the page is refreshing, please wait until the page refreshes and then perform actions ...
  31. The Web project %0 must be converted to the new Web site format. If you continue with this open from source control the project ...
  32. The web project %0 will be treated as uncontrolled because it was converted to the new Web site format. If you want source ...
  33. The Web request '{0}' completed successfully without running the test. This can occur when configuring the Web application ...
  34. The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server. ...
  35. The web server has been locked down and is blocking the DEBUG verb, which is required to enable debugging. Please see Help ...
  36. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the ...
  37. The web server process that was being debugged has been terminated by Internet Information Services (IIS). This can be avoided ...
  38. The web services enumeration components are not available. You need to reinstall Visual Studio to add web references to your ...
  39. The web site could not be configured correctly; getting ASP.NET process information failed. Requesting '{0}' returned an ...
  40. The web site could not be configured correctly; getting ASP.NET process information failed. The server may not be running ...
  41. The Web site path '{0}' does not exist. Tests configured to run in ASP.NET Development Server must specify a valid path to ...
  42. The Web site path '{0}' does not exist. Tests configured to run in ASP.NET Development Server must specify a valid path to ...
  43. The Web test '{0}' defines a column for data source table (Data Source: '{1}' Table: '{2}' Column: '{3}' )that is not included ...
  44. The Web Test Recorder browser extension is not properly installed. This prevents the Web Test Recorder from starting automatically. ...
  45. The Web test {0} was stopped because it encountered an excessive number of exceptions while attempting to submit requests ...
  46. The web version of the '{0}' has not been implemented for this release. You may still be able to use Team Web Access to edit ...
  47. The web.config file for the site {0} contains information from a previous run. Replacing it with the backup file ({1}) should ...
  48. The web.config file for the site {0} contains information from a previous run. The web.config file was generated, so deleting ...
  49. The web.config file has been set up with an assemblyPostProcessor different than {0}. Only one assemblyPostProcessor attribute ...
  50. The website metabase contains unexpected information or you do not have permission to access the metabase. You must be a ...
  51. The window search cannot be created. The specified parent control type is not supported. Supported parent types include FrameworkElement, ...
  52. The Windows Azure SDK for .NET must be installed to enable publishing to Windows Azure. LightSwitch will load a web page ...
  53. The Windows Firewall on this computer is currently blocking remote debugging. Remote debugging requires that the remote debugging ...
  54. The Windows Firewall on this machine is currently blocking remote debugging. Remote debugging requires that the debugger ...
  55. The Windows Firewall on this machine will be configured to allow remote debugging. The remote debugger (msvsmon.exe) must ...
  56. The Windows Installer service cannot update one or more protected Windows files. {SFP Error: 2]. List of protected files: ...
  57. The Windows Installer service cannot update the protected Windows file 2]. {Package version: 3], OS Protected version: 4], ...
  58. The Windows Installer service cannot update the system file 2 because the file is protected by Windows. You may need to update ...
  59. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows ...
  60. The Windows Installer service is unavailable. Another application may be running setup. Finish any installations in progress, ...
  61. The Windows Rights Management Services Client (RMS) is required in order for you to be able to open and create XPS documents ...
  62. The Windows Web Services API installation completed, but a reboot is required before the API is available. This computer ...
  63. The WmAppManifest.xml is not part of the project. All Windows Phone projects must have this manifest file. Please either ...
  64. The work associated with this review is not currently active. Activate it now](Switch to the task associated with this code ...
  65. The work item cannot be created because the current session or result is not valid. Close the current activity and launch ...
  66. The work item could not be moved to the sprint or backlog because an error occurred when attempting to update the iteration ...
  67. The work item could not be updated. An error occurred while attempting to update the required fields of the work item. The ...
  68. The work item has been modified on Team Foundation Server in the middle of publish process. Refresh the document, re-apply ...
  69. The work item store is not configured correctly. You must have at least one work item type in the category with reference ...
  70. The Work Item Tracking database refers to build Uris that cannot be resolved. These builds may have been deleted. Work items ...
  71. The work items linked to this model element are in these servers: {0}. To see the linked work items, connect Team Explorer ...
  72. The workflow instance accepted a stop request but did not complete within {0}. This may indicate an AsyncCodeActivity is ...
  73. The workflow instance did not accept a stop request within {0}. This typically indicates that a CodeActivity is blocking ...
  74. The working folder(s) of the existing workspace '{0}' cannot be unmapped to create a temporary workspace for uploading the ...
  75. The worksheet you are trying to change is protected and therefore read-only. To remove protection, click Excel in the designer, ...