Visual Studio 2013

  1. There is no metadata file available in which to save test list information. Please open a solution or metadata file before ...
  2. There is no network adapter on the virtual machines that is connected to a logical network. Modify the virtual machine using ...
  3. There is no remote configured for this local repository. Establish the remote by publishing to the URL of an existing empty ...
  4. There is no SCVMM server associated with this project collection. Run TfsConfig /lab to inspect application-level SCVMM server ...
  5. There is not enough disk space on the volume '[2]' to continue the install with recovery enabled. 3 KB are required, but ...
  6. There is not enough free disk space for collection to continue (at least {0} is required). Would you like to specify an alternate ...
  7. There is uncalled code that is not externally visible and is not a known runtime entry point. If this violation fires in ...
  8. There should not be any lab information for a physical test environment, and there should be lab information for a non-physical ...
  9. There was a conflict between two files from the redist folder files going to the same target path "{0}" between the "{1}" ...
  10. There was a conflict between two redist files going to the same target path "{0}" within the "{1}" SDK. Choosing "{2}" over ...
  11. There was a conflict between two references with the same file name between the "{0}" and "{1}" SDKs. Choosing "{2}" over ...
  12. There was a conflict between two references with the same file name resolved within the "{0}" SDK. Choosing "{1}" over "{2}" ...
  13. There was a failure while initializing the %s source control provider. You cannot use this provider to perform source control ...
  14. There was a problem creating and initializing the processor for a directive named '{1}'. The type of the processor is {0}. ...
  15. There was a problem loading the Add-in file '%s'. Would you like to remove this Add-in file? If you choose yes, the file ...
  16. There was a problem or delay during the creation of your initial Team Project Collection. To check the status of the Team ...
  17. There was a problem reading metadata from '%1' ('%2'). IntelliSense may not work properly until the solution is reloaded. ...
  18. There was a problem registering a file change notification for '%1' ('%2'). IntelliSense may not work properly until the ...
  19. There was a problem updating your online license. Your license is getting stale and you will no longer be able to access ...
  20. There was a problem updating your online license. Your trial has expired. Check for an updated license or enter a product ...
  21. There was a problem updating your online license. Your trial has expired. Check for an updated license to continue using ...
  22. There was a problem updating your online license. Your trial will expire soon and you will no longer be able to access this ...
  23. There was a problem updating your online license. Your trial will expire soon and you will no longer be able to access this ...
  24. There was an error connecting to the following team project: {0}. Ensure that the project exists in the following Team Foundation ...
  25. There was an error creating a temporary file that is needed to complete this installation.{ Folder: 3]. System error code: ...
  26. There was an error deleting the project. Please try again and if the problem persists contact our support team at [email protected] ...
  27. There was an error in downloading the result file. Try the operation again. If the problem persists, contact Team Foundation ...
  28. There was an error in downloading the result file. Try the operation again. If the problem persists, contact Visual Studio ...
  29. There was an error in queuing your loadtest. Try the operation again. If the problem persists, contact Visual Studio Online ...
  30. There was an error opening Change Source Control dialog. To allow the solution to open, some of its projects were temporarily ...
  31. There was an error processing the data in the network profile (This generally indicates invalid data in the network profile). ...
  32. There was an error saving the component database to disk. This database is used to enhance the performance of the Add Remove ...
  33. There was an error trying to create a folder in the source control database using the default name. To continue adding the ...
  34. There was an error while importing the result file. Details : {0}. After correcting the problem open the results from Load ...
  35. There was an error while writing to the item %s. This item keeps track of the solution's location, and a failure to update ...
  36. There was an error with process template "{0}". Please select another template or contact your Team Foundation Server administrator ...
  37. There was an internal error when querying IIS 7.0 for profiling. Ensure that you have all of the following Internet Information ...
  38. There was an internal error when querying IIS 7.0 for profiling. Ensure that you have the following IIS 6 Management Compatibility ...
  39. There was an internal error when querying IIS for profiling. Ensure that you have Internet Information Services (IIS) and ...
  40. There was no Windows Azure project (.ccproj) detected in the solution. Continuous delivery to an Azure Cloud Service requires ...
  41. There was not enough data collected to calculate the overhead of one or more counters; overhead for these counters will be ...
  42. There were character conversion errors while saving the project file '%1'. Save the project file in Unicode or UTF-8 format ...
  43. There were character conversion errors while saving the solution file '%s'. Save the solution file in Unicode or UTF-8 format ...
  44. There were errors dropping "{0}" onto the designer. Dropping function parameters or columns onto the designer is not supported. ...
  45. There were errors dropping "{0}" onto the designer. Dropping Oracle packages onto the designer is not supported. To call ...
  46. There were errors dropping "{0}" onto the designer. Dropping stored procedure parameters or columns onto the designer is ...
  47. There were errors loading the process parameters for this definition. This may be due to the fact that some or all of the ...
  48. There were failures synchronizing following local files with the server. You might need to manually delete or rename these ...
  49. There were invalid characters in input that are potentially dangerous. Try again without any HTML or SQL related characters. ...
  50. There were no process templates on the team foundation server-the list of process template headers returned from the Team ...
  51. There were problems generating {0}. To resolve this problem, build the project, fix any errors, and then generate the DataSet ...
  52. There were problems instantiating {0}. To resolve this problem, build the project, fix any errors, and preview the data again. ...
  53. There were some errors while creating standard environments from physical environments in Team Foundation Server. Use the ...
  54. These are items open in editors that Microsoft Visual Studio cannot reload. Therefore, you may not be able to reliably perform ...
  55. These are more recently saved than the currently open documents and contain changes that were made before the application ...
  56. These charts allow you to quickly visualize how the sprint is progressing. On the left you can see if the work you have scheduled ...
  57. These files are not text files and cannot be opened in the comparison window. {0} {1} The contents of the two files are identical. ...
  58. These projects are either not supported or need project behavior impacting modifications to open in this version of Visual ...
  59. These projects can be opened in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them. ...
  60. These projects will be labeled as unavailable in Solution Explorer. Expand the project node to show the reason the project ...
  61. These properties are applicable only if you store the virtual machine as a template. To store this machine as a template, ...
  62. These properties cannot be edited from Microsoft Test Manager. To edit them, use System Center Virtual Machine Manager Console. ...
  63. These rules expand on the basic correctness rules to maximize the logic and framework usage errors that are reported. Extra ...
  64. These rules expand on the basic design guideline rules to maximize the usability and maintainability issues that are reported. ...
  65. These rules focus on enforcing best practices to make your code easy to understand and use. Include this rule set if your ...
  66. These rules focus on logic errors and common mistakes made in the usage of framework APIs. Include this rule set to expand ...
  67. These rules focus on problems that prevent data in your application from displaying correctly when used in different languages, ...
  68. These rules focus on the most common and critical problems in your C++ projects that support the Common Language Runtime, ...
  69. These rules focus on the most critical and common problems in your native code, including potential security holes and application ...
  70. These rules focus on the most critical problems in your C++ projects that support the Common Language Runtime, including ...
  71. These rules focus on the most critical problems in your code for which Code Analysis is the most accurate. These rules are ...
  72. These rules focus on the most critical problems in your code, including potential security holes, application crashes, and ...
  73. These rules focus on the most critical problems in your native code, including potential security holes and application crashes. ...
  74. These steps contain shared parameters. The references to these parameters will be removed. Do you want to delete these steps? ...
  75. Third party scripts and code linked to or referenced from this website are licensed to you by the parties that own such code, ...