Visual Studio 2013

  1. The assembly '{0}' for directive processor '{1}' was not granted the FullTrust permission set. Only trusted assemblies are ...
  2. The assembly '{0}' is listed on the command line. Assemblies should be referenced using a command line flag such as '-r'. ...
  3. The assembly module '%s' cannot be re-deployed because it was created outside of Visual Studio. Drop the module from the ...
  4. The assembly reference "{0}" could not be added to the project. This wizard will continue to run, but the resulting project ...
  5. The associated release path for the given release template must have its Acceptance step set as automated to allow automatic ...
  6. The associated source control plug-in is not installed or could not be initialized. Common causes for this error include ...
  7. The Association '{0}' has multiple SourceEntity elements. The BDC Model Designer does not support editing models containing ...
  8. The Association with name '{0}' has an invalid Type '{1}'. Associations can only have MethodInstance Type of AssociationNavigator, ...
  9. The Associations referred to in the AssociationGroup '{0}' do not have a consistent set of Source and Destination elements. ...
  10. The attempt to complete an operation on the remote device has timed out. Close the session and try again. If the problem ...
  11. The attempt to install {0} failed. You can try to install the required components again by restarting this Remote Configuration ...
  12. The attempt to unwind the callstack failed. Unwinding is not possible in the following scenarios: 1. Debugging was started ...
  13. The attempted command cannot be completed because the file '{0}' that must be modified cannot be changed. If the file is ...
  14. The attempted command cannot be completed because the file '{0}' that must be modified cannot be changed. If the file is ...
  15. The attribute 'AutoOpen(\"{0}\")' in the assembly '{1}' did not refer to a valid module or namespace in that assembly and ...
  16. The attribute '{0}' appears in both the implementation and the signature, but the attribute arguments differ. Only the attribute ...
  17. The attribute type "{1}" returned by the XPathQuery "{3}" is incompatible with MetaAttribute "{0}" which requires type "{2} ...
  18. The attribute type "{1}" returned by the XPathQuery "{3}" is incompatible with MetaAttribute "{0}" which requires type "{2}" ...
  19. The attribute type '{0}' has 'AllowMultiple=false'. Multiple instances of this attribute cannot be attached to a single language ...
  20. The AttributeUsage attribute specifies the targets that are valid for the attribute (see System.AttributeTargets), whether ...
  21. The authentication mode specified in the configuration file is not supported. Valid modes are 'Windows', 'Forms', and 'None'. ...
  22. The automatically saved settings file '%s' cannot be found. You can change this file on the 'Import and Export Settings' ...
  23. The automatically saved settings file '%s' is not available for write. You can change this file on the 'Import and Export ...
  24. The average elapsed time to execute a transaction in a load test. For Web test transactions, think time is included in the ...
  25. The average response time for a Web test page in a load test. The response time for a page includes the time to load any ...
  26. The average response time for a Web test transaction in a load test. 'Avg. Response Time' differs from 'Avg. Transaction ...
  27. The Average Test Time of {1} seconds for Scenario '{0}' is too large for tests to be executed at the rate of {2} tests per ...
  28. The average time to receive the first byte of a response to a Web test request, measured from the time the request was sent ...
  29. The average time to receive the last byte of a response to a Web test request, measured from the time the request was sent ...
  30. The average time waiting for an available connection before sending a Web test request. Waiting can occur when the user load ...
  31. The Azure Mobile Services SDK currently installed cannot be used to add the Mobile Services connected service. No HandlerManifest.xml ...
  32. The Azure Mobile Services SDK currently installed cannot be used to add the Mobile Services connected service. The expected ...
  33. The Azure Mobile Services SDK currently installed may be out of date and cannot be used to add the Mobile Services connected ...
  34. The back button and title have different styles when snapped in addition to more extensive changes: The query text becomes ...
  35. The back button and title have different styles when snapped, and the list representation is substituted for the grid displayed ...
  36. The back button and title have different styles when snapped, and the page initially hides details to show only the list ...
  37. The Backup and Restore Power Tool has been replaced by the Scheduled Backups feature of Team Foundation Server. The Backup ...
  38. The Backup and Restore Power Tool settings discovered on this machine are invalid. Configuration of scheduled backups cannot ...
  39. The base for the storage URLs. Should be set to core.windows.net for the production cluster and to core.windows-int.net for ...
  40. The base URL for the Azure management service. Should be set to https://management.core.windows.net for the production cluster ...
  41. The baseline selected appears to be from a different process than the current view, comparisons may not be valid. Current: ...
  42. The baseline selected appears to be from a different process than the current view. Comparisons might not be valid. Current: ...
  43. The baseline selected represents a different instance of {0}' than the current view, comparisons may not be valid. Are you ...
  44. The baseline selected represents a different instance of {0}' than the current view. Comparisons might not be valid. Are ...
  45. The BDCModel Designer lets you visualize and design your BDC Model. Create new entities in the model by dragging items from ...
  46. The best overloaded method match '%1!ls!' for the collection initializer element cannot be used. Collection initializer 'Add' ...
  47. The best overloaded method match for '%1!ls!' has wrong signature for the initializer element. The initializable Add must ...
  48. The bind operation will ignore file differences. Your files may be replaced silently by their server versions on future source ...
  49. The bind operation will scan all your files to detect differences (This may take several minutes to complete). These files ...
  50. The binding information for project %1 could not be retrieved from its source control provider. This project may have been ...
  51. The binding information for this solution could not be retrieved from its source control provider. This solution may have ...
  52. The body of the page in most view states uses an items controls to create multiple radio buttons for filtering above a horizontal ...
  53. The bottom part of the view offers profile reports for all the non-hidden threads in the currently visible time range: 'Execution' ...
  54. The browser cannot open the following location due to this browser's security settings. You will need to copy the location ...
  55. The browser will try to open the build log file. The operation may not succeed due to this browser's security settings. The ...
  56. The browser will try to open the following location. However, the operation may not succeed due to this browser's security ...
  57. The browsing database in this directory is open by another instance of Visual Studio and cannot be reopened. User %1 on %2 ...
  58. The buffer pointed to by the lpstrFile member of the OPENFILENAME structure is too small for the filename specified by the ...
  59. The bug field mapping has been modified by another user or session. You must reload the bug field mapping and update it again. ...
  60. The bugfieldmapping command provides the ability to import or export the XML file that maps auto generated bug fields to ...
  61. The Bugs dashboard gives you an overview of the team's progress toward finding and fixing bugs. For information on how to ...
  62. The Bugs dashboard gives you an overview of the team's progress toward finding and fixing bugs. For information on how to ...
  63. The build administrators group does not exist for this collection. Permissions may not be set on groups that do not exist. ...
  64. The build agent {0} cannot be added to build controller {1} because either the build agent or the build controller is virtual. ...
  65. The Build Agent {1} is running as a different user {2} and local paths can only be mapped to a single workspace. To resolve ...
  66. The build associated with this IntelliTrace log file has published symbol files to "{0}". This location will be searched ...
  67. The build associated with this IntelliTrace log file no longer exists. You may have to enter the symbol path for this debugging ...
  68. The build associated with this IntelliTrace log file was not configured to publish symbols to a symbol server. You may have ...
  69. The build cannot start while code metrics calculation is in progress. Do you want to cancel? Click Yes to cancel code metrics ...
  70. The build controller cannot deserialize the process parameters of the build. Make sure the process parameters are compatible ...
  71. The build controller cannot download a build process template because the build server has reached the maximum number of ...
  72. The build controller used for this build does not support the version of the template file used by the build definition. ...
  73. The build controller {0} does not contain an enabled build agent with name {1} and matching Team Foundation Build version. ...
  74. The Build dashboard helps you monitor and measure how builds are progressing. For information on how to use this dashboard ...
  75. The Build dashboard helps you monitor and measure how builds are progressing. For information on how to use this dashboard ...