Opened 14 years ago
Last modified 12 years ago
#1595 closed Feature Request
New AutoIt3Wrapper directive - supportedOS ID for manifest — at Initial Version
Reported by: | sklocke | Owned by: | |
---|---|---|---|
Milestone: | 3.3.9.5 | Component: | Aut2Exe |
Version: | Severity: | None | |
Keywords: | manifest windows7 | Cc: |
Description
Introduction
With Windows 7, Microsoft introduces a new section in an application's manifest called Compatibility. In this section, entries supportedOS ID=<fixed value for OS> can be entered.
Currently, there exist fixed values for Windows Vista and Windows 7. Under Windows Vista and XP, this section is ignored.
One effect an entry for Windows 7 made in this section has is to disable the Program Compatibility Assisstant dialog that comes up under certain conditions and sometimes wrongly suggests to restart an executable in XP mode (which could break automated installation processes). I do not know all other effects, but Microsoft will at least tie down level support to these entries.
Feature request
Add a directive to the AutoIt3Wrapper that offers to respectively include the Windows 7 or Windows Vista ID in this section of the manifest. This would work similar to the #AutoIt3Wrapper_Res_requestedExecutionLevel directive, which already modifies the manifest embedded in the executable.
#AutoIt3Wrapper_Res_supportedOSWin7 #AutoIt3Wrapper_Res_supportedOSWinVista
would add
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!--The ID below indicates application support for Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> <!--The ID below indicates application support for Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> </application> </compatibility>
to the manifest, with the option to use only one of these dirctives.
For a related forum thread, including a discussion of a workaorund, see http://www.autoitscript.com/forum/index.php?showtopic=113657