Developers: Runtime Manifests

[Eagle]

1. Compatibility section for Windows 8

2. DPI aware -tell windows 6 and later to leave your GUI sizing alone

<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
		<application>
			<!--Windows Vista Support -->
				<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
			<!--Windows 7 Support -->
				<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
			<!--Windows 8 Support -->
				<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
		</application>
	</compatibility>
	<application xmlns="urn:schemas-microsoft-com:asm.v3">
		<windowsSettings>
			<ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings" xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true
			</ms_windowsSettings:dpiAware>
		</windowsSettings>
	</application>

[gremlin]

do you mean this will fix the boarder problem ? and is this the new part

<!--Windows 8 Support -->
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>

?

[Eagle]

should be YES to both, try the DPI addition and lets know how you go.

the DPI addition is known to inform windows to not play with font and window(hwnds of app gui) resizing
do to resolution settings of system display.

[gremlin]

Sadly I no longer have my laptop with windows 8 but I will soon as I move after Xmas reinstall it on my best PC and test this out, there are others that have windows 8 so lets hope they are able to test thanks for the heads up tho

But anyone should be able to update there mainfraim with RezHacker to test this out on 8 very easily

[Eagle]

BACKUP the original 3 manifest bin files in the data folder of AMS installation

simply edit a copy of each using notepad or similar and rename to original file names, rebuild(publish) your project and test.

[gremlin]

You can do that but if you wanted to just test without messing you can just use reshack as that makes a backup of your exe anyway and this will tell you if its going to work, if your happy its going to well then you can move to adding it to AMS's default files, its all about testing first lol.


Lets hope the next update will include this

I hope after xmas I start to use AMS more

[Eagle]

for sure: here's a better manifest layout for the DPI section:

<asmv3:application xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
    <asmv3:windowsSettings
         xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
      <dpiAware>true</dpiAware>
    </asmv3:windowsSettings>
  </asmv3:application>

ref:

http://msdn.microsoft.com/en-us/library/windows/desktop/dd464660%28v=vs.85%29.aspx#declaring_dpi_awareness

[Eagle]

here's a fully 'updated' invokermanifest.bin for AMS v8.0.7.0

[Sbleck]

Hi, Eagle,

here's a fully 'updated' invokermanifest.bin for AMS v8.0.7.0

Thanks very much in sharing this solution/help, because helped me to solve another problem when I tried to build an application with AMSP 8.0.7 in Windows Vista (Home Basic), when selecting to Publish -> Build -> Accept -> Web/Email executable -> Next and checked to "Encrypt data segment". Without this updated "invokermanifest.bin", I received back only "Failed to add application manifest" errors, when trying to build any app...

But only 7 viewed this, until now. Maybe this comment could help anothers too, with the same problem...

HTH,
Sven