Visual Studio 2013

  1. Contract '{0}' is not compatible with portable libraries because it contains one or more operations that have '{1}' or '{2}' ...
  2. Control %1 could not reload its state from its data saved from the last time the dialog editor was used. The control will ...
  3. Control cannot be bound to the new data source because it is bound to an XML schema that is mapped to the document. XML schema ...
  4. Control flow analysis is currently disabled. Enabling this : functionality will increase the number of code correctness : ...
  5. Control is not ready yet. Use ready function to add your callback to the ready list which will be executed whenever the control ...
  6. Control location '{0}' is invalid. Only English letters, period (.) character, and 'Controls._children' can be used to specify ...
  7. Control names must be unique and cannot differ only by lower case or upper case. This follows the standard coding guidelines. ...
  8. Controller '{0}' is only being used to collect data and diagnostics for this test run. You must add a diagnostic data adapter ...
  9. Controller cannot be configured to run as Local System when configured with hosted Team Foundation Server or when it uses ...
  10. Controller failed to copy instrumented code coverage file '{0}' to result directory. Code coverage analysis will be incomplete. ...
  11. Controls in this category are unavailable for the .NET Framework 4 Client Profile. To change this setting, in the Project ...
  12. Controls in this category are unavailable for the .NET Framework 4 Client Profile. To change this setting, open the Project ...
  13. Conversion from pointer-to-member of derived class to pointer-to-member of base class requires an explicit cast (other than ...
  14. Conversion is a valid standard conversion, which can be performed implicitly or by use of static_cast, C-style cast or function-style ...
  15. Conversion of the source control binding for one of the projects could not be completed. It is possible that a source control ...
  16. Conversion requires a constructor or user-defined-conversion operator, which can't be used by const_cast or reinterpret_cast ...
  17. Conversion rules for arithmetic operations in the comparison at %s(%d) mean that one branch cannot be executed in an inlined ...
  18. Conversion rules for arithmetic operations in the comparison at %s(%d) mean that one branch cannot be executed. Cast '%s' ...
  19. Converting solutions is unsupported for this pre-release version! Please convert the projects individually, and manually ...
  20. Copies an item or set of items, including metadata and version control history, from one location to another in Team Foundation ...
  21. Copy Local Satellite Assemblies : Specifies if the satellite assemblies of the reference will be automatically copied to ...
  22. Copy Local Satellite Assemblies|Specifies whether to automatically copy the referenced assembly's satellite assemblies to ...
  23. Copy Local|Specifies whether to automatically copy the referenced assembly to the target location during a build.|Build Properties ...
  24. Copy template URL to the clipboard. This URL can be used to create a new workitem with the same field values as the current ...
  25. Copy the last row in the table down below to make the # of rows the same as Days in Iteration. If Table has more rows then ...
  26. Correct the casing of '{0}' in assembly name {1} by changing it to '{2}'. '{2}' is an abbreviation and therefore is not subject ...
  27. Correct the casing of '{0}' in member name {1} by changing it to '{2}'. '{2}' is an abbreviation and therefore is not subject ...
  28. Correct the casing of '{0}' in namespace name '{1}' by changing it to '{2}'. '{2}' is an abbreviation and therefore is not ...
  29. Correct the casing of '{0}' in type name {1} by changing it to '{2}'. '{2}' is an abbreviation and therefore is not subject ...
  30. Correct the declaration of {0} so that it correctly points to an existing entry point in {1}. The unmanaged entry point name ...
  31. Correct the following problems and then run setup again. To learn more, you can review the list of !$!http://go.microsof ...
  32. Could not access the following location using the lab service account: {1}\{2}, {0}. Make sure that the lab service account ...
  33. Could not access the following location using the lab service account: {1}\{2}, {0}. Reason: {3}. Make sure that the lab ...
  34. Could not add a certificate to the personal certificate store. To finish building, open the Project Designer, click the Signing ...
  35. Could not add a reference to '{0}' for one of the following reasons: - Targets a higher version of the .NET Framework - Not ...
  36. Could not add a reference to: {0} For one of the following reasons: - Targets a higher version of the .NET Framework - Not ...
  37. Could not add an instance of {0} to the designer. To resolve this problem, build the project, fix any errors, and add the ...
  38. Could not attach to the ASP.NET server process. There is already a debugger attached to the ASP.NET process on that server. ...
  39. Could not attach to the Profiler Monitor. Make sure the VSPerfMon.exe is running in TRACE mode. Use /USER option if necessary. ...
  40. Could not automatically discover any SQL Server instances. Choose Register SQL Server Instance from the shortcut menu if ...
  41. could not be found. Using {1} instead. For best analysis results please ensure that the correct .NET Framework is installed. ...
  42. could not be saved to the specified location. Please select a different location or check that you have appropriate permissions ...
  43. could not be saved to the specified location. Please select a different location or check that you have appropriate permissions ...
  44. Could not connect to Load Test results database. 1. If SQL Server is not installed on the local machine, you can download ...
  45. Could not connect to Load Test results database. Check that the Load Test result database specified by the connection string ...
  46. Could not connect to remote machine '{0}'. Please make sure Remote Tools for Visual Studio 2013 is running and configured ...
  47. Could not connect to Team Foundation server because Team Explorer is not installed on this computer. Install Team Explorer ...
  48. Could not connect to the following test controller: {0}. The test controller may be unavailable, or it may be the incorrect ...
  49. Could not connect to the test controller '{0}'. Make sure the test controller is online and since you are connected to a ...
  50. Could not connect to the Web server for page '{0}'. {1}. Check that the Web server is running and visible on the network ...
  51. Could not copy the test assembly's application configuration file from '{0}' while setting up assembly resolution settings. ...
  52. Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  53. Could not create or move file '%1'. The number of characters in the complete path name exceeds the file system limits. Reduce ...
  54. Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  55. Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...
  56. Could not determine the protocol used for this gallery. The URL must point to an Atom Feed or Sharepoint List configured ...
  57. Could not determine whether '%1' is a multifile assembly. The assembly manifest may be corrupt. Assuming a non-multifile ...
  58. Could not find a Code Snippet titled 'Method Stub - Body', or could not find a literal in that snippet whose ID is 'signature'. ...
  59. Could not find a field named '{0}' in the SpecificFinder view of the Entity. Please verify the name of the Action Parameter. ...
  60. Could not find a MethodInstance with the name '{0}' in the Method '{1}'. Please verify the value of MethodInstanceName attribute ...
  61. could not find a running emulator or more than one emulator instances were found running. To use {0}, ensure that a single ...
  62. Could not find a snippet titled 'Method Stub - Body' or 'Method Stub - No Body', or could not find a literal in that snippet ...
  63. Could not find a wrapper assembly for the COM component '%1'. %2 You can choose to create your own wrapper or a custom wrapper ...
  64. Could not find an implementation of the query pattern for source type '%1!ls!'. '%2!ls!' not found. Are you missing a reference ...
  65. Could not find an implementation of the query pattern for source type '%1!ls!'. '%2!ls!' not found. Consider explicitly specifying ...
  66. could not find assembly '%s': please specify the assembly search path using /AI or by setting the LIBPATH environment variable ...
  67. Could not find assembly to display link type '{0}'. This could happen if component required to edit that type is not installed. ...
  68. Could not find Microsoft {0} SDK {1}. Please make sure that the correct version of the Microsoft {0} SDK has been installed. ...
  69. Could not find rule assembly or directory "{0}" specified in CodeAnalysisRuleAssemblies for the "{1}" configuration. Some ...
  70. Could not find test executor with URI '{0}'. Make sure that the test executor is installed and supports .net runtime version ...
  71. Could not find test plan with ID {0}. Make sure the test plan exists under team project '{1}' and you have the right permissions. ...
  72. Could not find test suite with ID {0}. Make sure the test suite exists under team project '{1}' and you have the right permissions. ...
  73. Could not find the commit in the current active repository. Please switch to the correct repository to view the commit details. ...
  74. Could not find the component required to edit this link type. Make sure the component or tool needed to edit this link type ...
  75. Could not find the return parameter with name '{0}' specified on the MethodInstance named '{1}' in the Method named '{2}'. ...