Visual Studio 2012

  1. APPX3021: App manifest validation failed. Value '{0}' of {1} must contain only characters a-z, A-Z, 0-9, dash, underscore, ...
  2. APPX3025: App manifest validation failed. Value '{0}' of {1} must be a valid device capability. It can either a GUID or must ...
  3. APPX3026: App manifest validation failed. Value '{0}' of {1} is not a valid foreground text value. Valid values are 'light' ...
  4. APPX3027: App manifest validation failed. Value '{0}' of {1} must be either 'allLogos', 'noLogos', 'logoOnly', or 'wideLogoOnly'. ...
  5. APPX3028: App manifest validation failed. Value '{0}' of {1} must be either 'portrait', 'landscape', 'portraitFlipped', or ...
  6. APPX3031: App manifest validation failed. Value '{0}' of {1} is not a valid short display name. It should have up to 40 characters, ...
  7. APPX3032: App manifest validation failed. Value '{0}' of {1} is not a valid ASCII Windows ID. It must contain one or more ...
  8. APPX3034: App manifest validation failed. Value '{0}' of {1} is not a valid file type. It must start with a period and have ...
  9. APPX3035: App manifest validation failed. Value '{0}' of {1} is not a valid protocol. It must contain only characters a-z, ...
  10. APPX3036: App manifest validation failed. Value '{0}' of {1} is not a valid executable name. It must have extension '.exe'. ...
  11. APPX3038: App manifest validation failed. Value '{0}' of {1} is not a valid content type. It must contain only characters ...
  12. APPX3039: App manifest validation failed. Value '{0}' of {1} is not a valid content type. It should consist of two parts ...
  13. APPX3040: App manifest validation failed. Value '{0}' of {1} is not a valid file type association name. Spaces and uppercase ...
  14. APPX3041: App manifest validation failed. Value '{0}' of {1} is not a valid activatable class attribute type. Valid values ...
  15. APPX3042: App manifest validation failed. Value '{0}' of {1} is not a valid interface name. Backslashes, dashes, and spaces ...
  16. APPX3043: App manifest validation failed. Value '{0}' of {1} is not a valid instancing flag. Valid values are 'singleInstance' ...
  17. APPX3044: App manifest validation failed. Value '{0}' of {1} is not a valid threading model. Valid values are 'both', 'STA', ...
  18. APPX3045: App manifest validation failed. Value '{0}' of {1} is not a valid background task name. Valid values are 'audio', ...
  19. APPX3047: App manifest validation failed. Value '{0}' of {1} is not a valid auto play event. It cannot start with a backslash. ...
  20. APPX3048: App manifest validation failed. Supported file types element {0} must have either one or more FileType elements, ...
  21. APPX3051: App manifest validation failed. The extension element with category attribute value "windows.shareTarget" must ...
  22. Architectural analysis found internal errors. Results might not be complete. For more information, see the detailed build ...
  23. archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended ...
  24. Are you sure that you want to change the SCVMM server name for the Tfs project collection? Currently configured SCVMM server ...
  25. Are you sure that you want to remove '{0}' account? If you do so, then other Application Tiers that use this account as the ...
  26. Are you sure that you want to remove the integration settings? If you remove these settings, team projects and team project ...
  27. Are you sure that you want to remove this Web application from Team Foundation Server? If you do so, any project sites contained ...
  28. Are you sure that you want to update the default column settings? If you choose OK, these settings will be applied to all ...
  29. Are you sure you want to cancel publishing this test run? All data for this run will be removed from the Team Foundation ...
  30. Are you sure you want to delete %s? Please Note: Any project configurations that were created with this solution configuration ...
  31. Are you sure you want to delete everything about build '{0}' including details, files and folder under drop folder, test ...
  32. Are you sure you want to delete the default process template? The next process template in the list will become the default ...
  33. Are you sure you want to delete the selected item(s)? To add the deleted item(s) back, you will need to run TfsMgmt.exe on ...
  34. Are you sure you want to delete the selected node and all of its child nodes? This area may currently be used to categorize ...
  35. Are you sure you want to delete the selected node and all of its sub nodes? This area may currently be used to categorize ...
  36. Are you sure you want to delete the selected workspaces? All pending changes in the selected workspaces will be lost. This ...
  37. Are you sure you want to delete the suspended work named '{0}' and its backing shelveset '{1}'? This operation is permanent. ...
  38. Are you sure you want to destroy the {0} work item type as well as its {1} work item(s)? This action is not recoverable. ...
  39. Are you sure you want to remove public message queue "{0}" from machine "{1}"? Note: Deleting a public queue can take some ...
  40. Are you sure you want to restore to the previous snapshot? The current state of the environment will be lost. If any tests ...
  41. Are you sure you want to restore to the snapshot '{0}'? The current state of the environment will be lost. If any tests are ...
  42. Argument '%1$d': using a read-only string as a writable string argument. This will attempt to write into static read-only ...
  43. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe ...
  44. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe ...
  45. Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions ...
  46. Arguments '{0}' are not valid. Markup extensions require one equal sign between name and value, and one comma between constructor ...
  47. Arguments '{0}' are not valid. Markup extensions require only spaces between the markup extension name and the first parameter. ...
  48. Array method '{0}' is supplied by the runtime and cannot be directly used in code. For operations with array elements consider ...
  49. Artifacts associated with this layer must belong to one of the specified namespaces. Use a semicolon to separate multiple ...
  50. Artifacts associated with this layer must not belong to the specified namespaces. Use a semicolon to separate multiple namespaces. ...
  51. Artifacts associated with this layer must not depend on the specified namespaces. Use a semicolon to separate multiple namespaces. ...
  52. As it is declared in your code, parameter {0} of P/Invoke {1} will be {2} bytes wide on {3} platforms. This is not correct, ...
  53. As it is declared in your code, the return type of P/Invoke {0} will be {1} bytes wide on {2} platforms. This is not correct, ...
  54. As part of TFS configuration IIS dynamic compression was enabled to improve performance. This is a system-wide setting for ...
  55. As part of the backup schedule, you can also backup the SQL Server Reporting Services databases. A different server might ...
  56. As part of the backup schedule, you can also specify databases that SharePoint Products use. A different server might host ...
  57. ASM List Location : Specifies relative path and/or name for ASM listing file; can be file or directory name. (/Fa[name]) ...
  58. ASP debugging is disabled because the ASP process is running as a user that does not have debug permissions. Please see Help ...
  59. ASP.NET debugging is not enabled for this web. You can set 'debug' to True in the web's configuration file to enable debugging. ...
  60. Assemblies should explicitly state their CLS compliance using the CLSCompliant attribute. An assembly without this attribute ...
  61. Assemblies should use version numbers. The version number is considered part of an assembly's identity. Versioning is applied ...
  62. Assemblies that reference System.Windows.Forms should have the STAThreadAttribute. Failure to apply this attribute will most ...
  63. Assembly '{0}' not found in dependency set of target binary. Statically linked roots should be specified using an assembly ...
  64. Assembly '{0}' was not found. Verify that you are not missing an assembly reference. Also, verify that your project and all ...
  65. Assembly '{0}' was referenced transitively and the assembly could not be resolved automatically. Static linking will assume ...
  66. Assembly '|1' references assembly '|2', which is ambiguous between '|3' (referenced by project '|4') and '|5' (referenced ...
  67. Assembly and module attributes must precede all other elements defined in a file except using clauses and extern alias declarations ...
  68. Assembly keyword Specifies that an attribute at the beginning of a source file applies to the entire assembly. Otherwise ...
  69. Assembly Link Resource : Links a resource file to the output assembly. The resource file is not placed in the output assembly, ...
  70. Assembly metadata will be loaded into the folder path "{0}". Any nonexistent folders in the folder path have been created. ...
  71. Assembly must be specified for XAML files that are not part of a project. Reopen this XAML file after adding it to a project, ...
  72. Assembly {0} has a reference to assembly '{1}'. Because this assembly was introduced in {2}, which is higher than the project's ...
  73. Assembly {0} is marked with an attribute that uses member {1}. Because this member was introduced in {2}, which was not included ...
  74. Assembly {0} is marked with an attribute that uses type {1}. Because this type was introduced in {2}, which was not included ...
  75. Assembly.GetEntryAssembly() returns null. Set the Application.ResourceAssembly property or use the pack://application:,/assemblyname;component/ ...