add maxversiontested to AutoIt's app manifest

[MattyD]

Hi guys, I understand if this a bit on the obscure side - but would it be possible to add a "maxversiontested" element into AutoIt's application manifest? It would be to lend support for XAML Islands.

The proposed value is:
<maxversiontested Id="10.0.18362.1"/>

Discussion is here:
​https://www.autoitscript.com/forum/topic/212864-mediaplayerelement-winrt-xaml-island/page/2/#comments

Thanks,
Matt

[Jpm]

Should the manifest for AutoIt3.exe and AUt2exe.exe be changed to

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" language="*" processorArchitecture="*" publicKeyToken="6595b64144ccf1df"/>
    </dependentAssembly>
  </dependency>
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <maxversiontested Id="10.0.18362.1"/>
      <!-- Windows Vista -->
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
      <!-- Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <!-- Windows 8 -->
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
      <!-- Windows 8.1 -->
      <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
      <!-- Windows 10 --> 
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    </application>
  </compatibility>
</assembly>

[Jos]

Yes, but only when the target OS is Win10, so assume only when this is part of the source:

#pragma compile(Compatibility, win10)

Doubt we should change the manifest for AutoIt3.exe and make this general setting for all ran scripts and assume everything will keep on working on win11+:
Thoughts?

[MattyD]

Fair enough, I can understand not wanting to bake this in. The problem is more around running scripts from the IDE though. So I wouldn't think we could solve that without altering the manifests in the Autoit bins?

On the Win11+ question - for later builds, MS says: "you should either leave the 10.0.18362.0 value as is, or add multiple maxversiontested elements for the different values the app supports." (the actual release of win10 1903 is 10.0.18362.1).

​https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/xaml-islands/host-standard-control-with-xaml-islands-cpp (point 5b)

I've been using this value with win11 24H2 so far without issue (touch wood) - albeit we haven't really tested a variety of controls.