Visual Studio 2012

  1. Appends two inputs. You can use this to raise a vector that has two or three components to the next higher dimension, or ...
  2. Application does not require a console, probably because it creates its own windows for interaction with the user. If WinMain ...
  3. Application launch failed. Ensure that the device screen is unlocked and device is developer unlocked. For details on developer ...
  4. Application launch failed. Ensure that the device screen is unlocked and device is developer unlocked. For details on developer ...
  5. Application library caching cannot be used by out-of-browser applications. Do you want to enable application library caching ...
  6. Application library resource assembly {0} has missing or unknown download uri metadata and won't be packaged into the zip ...
  7. Application manifest file not found. Make sure that the WMAppManifest.xml file is present and is not excluded from the project. ...
  8. Application Mappings : The semicolon-separated list of file extensions to be associated with the primary project output. ...
  9. Application Page items are added to the following folder: {0}. An item with the specified name already exists in that folder. ...
  10. Application Protection : The level of process isolation used by the virtual directory. Value is set only when the virtual ...
  11. Application settings allow you to store and retrieve property settings and other information for your application dynamically. ...
  12. Application verifier has triggered a breakpoint in %1. This is an error in %2 or any of the DLLs it has loaded. Please see ...
  13. Application verifier has triggered a breakpoint in %s. This is an error in %s or any of the DLLs it has loaded. Please see ...
  14. Applications cannot be launched under the debugger when the remote debugger is running as a service. Run the Remote Debugger ...
  15. Applications hosted on Windows Azure using Windows authentication require additional configuration on your Azure account. ...
  16. Applies changes from one branch into another. tf merge /recursive /force /candidate /discard /version:versionspec /lock:(none|checkin|checkout) ...
  17. Apps designed to run on Windows 8 should support displays of different resolutions. Windows provides a simple way to do this ...
  18. APPX0004: This Windows Store app could not be packaged. You can only package Windows Store apps on computers that have the ...
  19. APPX0101: A signing key is required in order to package this project. Please specify a PackageCertificateKeyFile or PackageCertificateThumbprint ...
  20. APPX0102: A certificate with thumbprint '{0}' that is specified in the project cannot be found in the certificate store. ...
  21. APPX0103: More than one certificate has been found that matches the PackageCertificateThumbprint value in the project file. ...
  22. APPX0105: Cannot import the key file '{0}'. The key file may be password protected. To correct this, try to import the certificate ...
  23. APPX0107: The certificate specified is not valid for signing. For more information about valid certificates, see http:// ...
  24. APPX0108: The certificate specified has expired. For more information about renewing certificates, see http://go.microsoft.com/fwlink/?LinkID=241478. ...
  25. APPX0505: The processor architecture of your project '{0}' doesn't match the processor architecture '{1}' of the referenced ...
  26. APPX1403: Validation failed. See event log 'Applications and Services Logs/Microsoft/Windows/AppxPackagingOM/Microsoft-W ...
  27. APPX1405: The XML content in the file '{0}' isn't well-formed. {1} To resolve the issue, do one of the following: 1) use ...
  28. APPX1502: The project contains {0} items that represent the app manifest: {1}. The project can contain only one app manifest. ...
  29. APPX1503: The project contains {0} item(s) that represent the app manifest: {1}. App manifests that are not used to produce ...
  30. APPX1601: The Publisher attribute of the Identity element in the app manifest must have the value of the Publisher ID value ...
  31. APPX1603: The PublisherDisplayName element of the Properties element in the app manifest must have the value of the Publisher ...
  32. APPX1604: The Version attribute of the Identity element in the app manifest must have a higher version number than '{0}'. ...
  33. APPX1606: All languages specified in the Language attribute of the Resource element in the app manifest must be supported ...
  34. APPX1608: The Name attribute of the Identity element in the app manifest must have the Package name value of the selected ...
  35. APPX1609: The package contains a Debug framework reference '{0}'. Ensure all framework references in the package are valid ...
  36. APPX1610: The app manifest must include at least one Windows Store certification language in the Language attribute of the ...
  37. APPX1611: The Package.storeassociation.xml file is invalid. To fix this problem, choose the "Associate App with the Store" ...
  38. APPX1612: App manifest defines both start page and either entry point or executable for {0} '{1}'. Only one of them can be ...
  39. APPX1617: App manifest references the {0} image '{1}' which has an unsupported extension. Extension must be JPG, JPEG, or ...
  40. APPX1620: App manifest references the {0} image '{1}' which is in the unsupported format '{2}'. It must be a JPEG or PNG ...
  41. APPX1621: A mixture of images matching logical name '{0}' exists in this project with and without the "scale" or "targetsize" ...
  42. APPX1627: App manifest declares document library access capability without specifying at least one file type association. ...
  43. APPX1647: App manifest contains a file type association or file picker contract with incorrect file type '{0}'. File type ...
  44. APPX1648: App manifest contains a file type association or file picker contract with incorrect file type '{0}'. File type ...
  45. APPX1649: App manifest contains a contract '{0}' with both FileType and SupportsAnyFileType elements. '{1}/SupportedFileTypes' ...
  46. APPX1650: App manifest contains a protocol contract with incorrect name '{0}'. Protocol name length should be between {1} ...
  47. APPX1652: App manifest contains a certificate contract with incorrect store name '{0}'. Store name length should not be more ...
  48. APPX1655: App manifest contains an {0} contract with incorrect verb '{1}'. Verb length should not be more than {2} characters. ...
  49. APPX1657: App manifest contains an {0} contract with incorrect action display name '{1}'. Action display name length should ...
  50. APPX1658: App manifest contains an {0} contract with incorrect verb '{1}'. Verb should not contain underscore character ('_'). ...
  51. APPX1661: App manifest contains an {0} contract with incorrect verb '{1}'. Verb should have only following characters: -. ...
  52. APPX1663: App manifest contains an {0} contract with incorrect value for {1} attribute: '{2}'. Event length should not be ...
  53. APPX1668: App manifest contains a background task contract which uses executable '{0}', but does not specify task type 'Control ...
  54. APPX1671: App manifest defines invalid lock screen notifications value '{0}' for {1}. Valid values are 'badge' or 'badgeAndTileText'. ...
  55. APPX1674: App manifest defines lock screen notifications without specifying one of appropriate background task types: timer, ...
  56. APPX1675: App manifest declares background task of type timer, control channel, or push notification without enabling lock ...
  57. APPX1680: In the app manifest, the element OSMaxVersionTested must have a value equal to or higher than the value of the ...
  58. APPX1681: The build property AppxOSMaxVersionTested must have a value equal to or higher than the value of the build property ...
  59. APPX1684: App manifest contains a background task contract that has task type 'Control Channel' but does not specify an executable ...
  60. APPX1685: Default language '{0}' is not valid. For a list of supported values, see http://go.microsoft.com/fwlink/?LinkID=252020. ...
  61. APPX1706: The .winmd file '{0}' contains type '{1}' outside its root namespace '{2}'. Make sure that all public types appear ...
  62. APPX1707: No implementation file was provided for the .winmd file '{0}'. To generate registration information in the app ...
  63. APPX1708: The executable '{1}' is specified as the implementation for the .winmd file '{0}'. Only in-process servers are ...
  64. APPX1709: The SDK manifest contains registration information for the .winmd file {0}, but there is more than one file with ...
  65. APPX1712: The .winmd file '{0}' contains duplicate type names. Type '{1}' is already registered with the in-process server ...
  66. APPX1713: To ensure the correct metadata resolution, the type '{1}' contained in .winmd file '{0}' should be located in '{2}.winmd'. ...
  67. APPX1715: The .winmd file '{0}' contains type '{1}' that uses interface '{2}'. You can't use interface '{2}' because it is ...
  68. APPX1901: The DefaultLanguage property is either missing from the project file or does not have a value. The fallback language ...
  69. APPX2002: Cannot find the neutral resource language for the resources for portable library '{0}'. Verify that the portable ...
  70. APPX3012: App manifest validation failed. Value '{0}' of {1} is not a valid description. It should have up to 2048 characters ...
  71. APPX3014: App manifest validation failed. Value '{0}' of {1} is not a valid file name. It cannot contain characters , ", ...
  72. APPX3015: App manifest validation failed. Value '{0}' of {1} is not a valid image file name. It should have extension png, ...
  73. APPX3017: App manifest validation failed. Value '{0}' of {1} is not a valid processor architecture. Supported values are ...
  74. APPX3018: App manifest validation failed. Value '{0}' of {1} is not a valid display name. It should have up to 256 characters, ...
  75. APPX3020: App manifest validation failed. Value '{0}' of {1} must contain only characters a-z, A-Z, 0-9, dash, and period. ...