Visual Studio 2013
- APPX1601: The Publisher attribute of the Identity element in the app manifest must have the value of the Publisher ID value ...
- APPX1603: The PublisherDisplayName element of the Properties element in the app manifest must have the value of the Publisher ...
- APPX1604: The Version attribute of the Identity element in the app manifest must have a higher version number than '{0}'. ...
- APPX1606: All languages specified in the Language attribute of the Resource element in the app manifest must be supported ...
- APPX1608: The Name attribute of the Identity element in the app manifest must have the Package name value of the selected ...
- APPX1609: The package contains a Debug framework reference '{0}'. Ensure all framework references in the package are valid ...
- APPX1610: The app manifest must include at least one Windows Store certification language in the Language attribute of the ...
- APPX1611: The Package.storeassociation.xml file is invalid. To fix this problem, choose the "Associate App with the Store" ...
- APPX1612: App manifest defines both start page and either entry point or executable for {0} '{1}'. Only one of them can be ...
- APPX1617: App manifest references the {0} image '{1}' which has an unsupported extension. Extension must be JPG, JPEG, or ...
- APPX1620: App manifest references the {0} image '{1}' which is in the unsupported format '{2}'. It must be a JPEG or PNG ...
- APPX1621: A mixture of images matching logical name '{0}' exists in this project with and without the "scale" or "targetsize" ...
- APPX1627: App manifest declares document library access capability without specifying at least one file type association. ...
- APPX1639: File '{0}' not found. See http://go.microsoft.com/fwlink/?prd=12395pver=1.0&plcid=0x409&ar=MSDN&sar=PlatformMultiTargeting&o1={1}&o2={2} ...
- APPX1647: App manifest contains a file type association or file picker contract with incorrect file type '{0}'. File type ...
- APPX1648: App manifest contains a file type association or file picker contract with incorrect file type '{0}'. File type ...
- APPX1649: App manifest contains a contract '{0}' with both FileType and SupportsAnyFileType elements. '{1}/SupportedFileTypes' ...
- APPX1650: App manifest contains a protocol contract with incorrect name '{0}'. Protocol name length should be between {1} ...
- APPX1652: App manifest contains a certificate contract with incorrect store name '{0}'. Store name length should not be more ...
- APPX1655: App manifest contains an {0} contract with incorrect verb '{1}'. Verb length should not be more than {2} characters. ...
- APPX1657: App manifest contains an {0} contract with incorrect action display name '{1}'. Action display name length should ...
- APPX1658: App manifest contains an {0} contract with incorrect verb '{1}'. Verb should not contain underscore character ('_'). ...
- APPX1661: App manifest contains an {0} contract with incorrect verb '{1}'. Verb should have only following characters: -. ...
- APPX1663: App manifest contains an {0} contract with incorrect value for {1} attribute: '{2}'. Event length should not be ...
- APPX1668: App manifest contains a background task contract which uses executable '{0}', but does not specify task type 'Control ...
- APPX1669: App manifest contains a background task contract which uses server name '{0}', but does not specify task type 'Control ...
- APPX1670: App manifest contains a background task contract which uses both executable '{0}' and server name '{1}'. Contract ...
- APPX1671: App manifest defines invalid lock screen notifications value '{0}' for {1}. Valid values are 'badge' or 'badgeAndTileText'. ...
- APPX1674: App manifest defines lock screen notifications without specifying one of appropriate background task types: timer, ...
- APPX1675: App manifest declares background task of type timer, control channel, push notification, or location without enabling ...
- APPX1680: In the app manifest, the element OSMaxVersionTested must have a value equal to or higher than the value of the ...
- APPX1681: The build property AppxOSMaxVersionTested must have a value equal to or higher than the value of the build property ...
- APPX1684: App manifest contains a background task contract that has task type 'Control Channel' but does not specify an executable, ...
- APPX1685: Default language '{0}' is not valid. For a list of supported values, see http://go.microsoft.com/fwlink/?LinkID=252020. ...
- APPX1686: App manifest contains invalid content URI rule '{0}'. The rule must begin with 'https://' if a scheme is present. ...
- APPX1688: App manifest contains a background task contract which uses both start page '{0}' and server name '{1}'. Contract ...
- APPX1706: The .winmd file '{0}' contains type '{1}' outside its root namespace '{2}'. Make sure that all public types appear ...
- APPX1707: No implementation file was provided for the .winmd file '{0}'. To generate registration information in the app ...
- APPX1708: The executable '{1}' is specified as the implementation for the .winmd file '{0}'. Only in-process servers are ...
- APPX1709: The SDK manifest contains registration information for the .winmd file {0}, but there is more than one file with ...
- APPX1712: The .winmd file '{0}' contains duplicate type names. Type '{1}' is already registered with the in-process server ...
- APPX1713: To ensure the correct metadata resolution, the type '{1}' contained in .winmd file '{0}' should be located in '{2}.winmd'. ...
- APPX1715: The .winmd file '{0}' contains type '{1}' that uses interface '{2}'. You can't use interface '{2}' because it is ...
- APPX1901: The DefaultLanguage property is either missing from the project file or does not have a value. The fallback language ...
- APPX2002: Cannot find the neutral resource language for the resources for portable library '{0}'. Verify that the portable ...
- APPX3012: App manifest validation failed. Value '{0}' of {1} is not a valid description. It should have up to 2048 characters ...
- APPX3014: App manifest validation failed. Value '{0}' of {1} is not a valid file name. It cannot contain characters , ", ...
- APPX3015: App manifest validation failed. Value '{0}' of {1} is not a valid image file name. It should have extension png, ...
- APPX3017: App manifest validation failed. Value '{0}' of {1} is not a valid processor architecture. Supported values are ...
- APPX3018: App manifest validation failed. Value '{0}' of {1} is not a valid display name. It should have up to 256 characters, ...
- APPX3020: App manifest validation failed. Value '{0}' of {1} must contain only characters a-z, A-Z, 0-9, dash, and period. ...
- APPX3021: App manifest validation failed. Value '{0}' of {1} must contain only characters a-z, A-Z, 0-9, dash, underscore, ...
- APPX3025: App manifest validation failed. Value '{0}' of {1} must be a valid device capability. It can either a GUID or must ...
- APPX3026: App manifest validation failed. Value '{0}' of {1} is not a valid foreground text value. Valid values are 'light' ...
- APPX3027: App manifest validation failed. Value '{0}' of {1} must be either 'allLogos', 'noLogos', 'logoOnly', or 'wideLogoOnly'. ...
- APPX3028: App manifest validation failed. Value '{0}' of {1} must be either 'portrait', 'landscape', 'portraitFlipped', or ...
- APPX3031: App manifest validation failed. Value '{0}' of {1} is not a valid short display name. It should have up to 40 characters, ...
- APPX3032: App manifest validation failed. Value '{0}' of {1} is not a valid ASCII Windows ID. It must contain one or more ...
- APPX3034: App manifest validation failed. Value '{0}' of {1} is not a valid file type. It must start with a period and have ...
- APPX3035: App manifest validation failed. Value '{0}' of {1} is not a valid protocol. It must contain only characters a-z, ...
- APPX3036: App manifest validation failed. Value '{0}' of {1} is not a valid executable name. It must have extension '.exe'. ...
- APPX3038: App manifest validation failed. Value '{0}' of {1} is not a valid content type. It must contain only characters ...
- APPX3039: App manifest validation failed. Value '{0}' of {1} is not a valid content type. It should consist of two parts ...
- APPX3040: App manifest validation failed. Value '{0}' of {1} is not a valid file type association name. Spaces and uppercase ...
- APPX3041: App manifest validation failed. Value '{0}' of {1} is not a valid activatable class attribute type. Valid values ...
- APPX3042: App manifest validation failed. Value '{0}' of {1} is not a valid interface name. Backslashes, dashes, and spaces ...
- APPX3043: App manifest validation failed. Value '{0}' of {1} is not a valid instancing flag. Valid values are 'singleInstance' ...
- APPX3044: App manifest validation failed. Value '{0}' of {1} is not a valid threading model. Valid values are 'both', 'STA', ...
- APPX3045: App manifest validation failed. Value '{0}' of {1} is not a valid background task name. Valid values are 'audio', ...
- APPX3047: App manifest validation failed. Value '{0}' of {1} is not a valid auto play event. It cannot start with a backslash. ...
- APPX3048: App manifest validation failed. Supported file types element {0} must have either one or more FileType elements, ...
- APPX3051: App manifest validation failed. The extension element with category attribute value "windows.shareTarget" must ...
- APPX3053: App manifest validation failed. Value '{0}' of {1} must be either 'default', 'useLess', 'useHalf', 'useMore', or ...
- APPX3054: App manifest validation failed. Value '{0}' of {1} must be either 'halfHour', 'hour', 'sixHours', 'twelveHours', ...
- APPX3057: App manifest validation failed. Value '{0}' of {1} must be either 'square150x150Logo', 'wide310x150Logo', or 'square310x310Logo'. ...