Add app compatibility GUID for Windows 8 to chrome, mini_installer, and setup's manifests

As per the "Windows 8 and Windows Server 2012 Compatibility Cookbook"'s "App (executable) manifest" entry at http://msdn.microsoft.com/en-us/library/windows/desktop/hh848036(v=vs.85).aspx, this will turn on:

Shell themes status in high contrast mode
Windows 8: Returns the real theming status for when in high contrast mode.
Windows 7: Returns theming as unavailable when in high contrast mode because DWM is still on.
Windows Vista (default): Returns theming as unavailable when in high contrast mode because DWM is still on.

Shell iPersistFile::Save method
Windows 8: CShellLink::Save now determines if the IPersistFile handler is called with a relative path argument and fails the call if it is.
The public documentation describing this behavior indicates that path argument has to be an absolute path:
Windows 7 and earlier (default): CShellLink::Save does not determine if the iPersistFile handler sends a relative path check and allows apps to continue working with absolute or relative paths.

Program Compatibility Assistant (PCA)
Windows 8: Apps with the compatibility section do not get the PCA mitigation.
Windows 7: Apps with the compatibility section are tracked for potential compatibility issues for Windows 8 changes (described in this document).
Windows Vista (default): Apps that fail to install properly or crash during runtime under some specific circumstances get the PCA mitigation. For more information, see the Resources section.

Everything else will remain the same as the already turned on Windows 7 behavior for Chrome.

BUG=127765
TEST=Build, install, and run Chrome on Windows 8.

Review URL: https://chromiumcodereview.appspot.com/10837344

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152552 0039d316-1c4b-4281-b951-d872f2087c98

0 files changed, 0 insertions, 0 deletions