Jimmy,

>interessing ... but what about old Apps ( not only Xbase++ ) ?
>MSDN say Windows 10 need Manifest with "supportedOS"

Of course, you don't need a manifest at all -- and many applications don't 
have one -- and you don't need the new <supportedOS> entry in your manifest 
file either.

>now try include OsVer.EXE ( v1.9.355) on Windows 10 and you will see 
>(green) it will tell you 10.0

But you are correct that adding a manifest with the "supportedOS" value for 
Windows 10 will tell the OS that your application was designed for (and 
tested on) Windows 10, and the OS will therefore return the correct OS 
version. But it will also treat your application as a Windows 10 app and 
will disable any compatibility options that would otherwise be enabled, 
which could have weird side-effects if your application depends on that 
older behavior.

Of course, if you use Xbase++ 2.00.623 or newer, you don't need a manifest 
with the new <supportedOS> XML element at all, and you will still get the 
correct Windows Version information from the Xbase++ OS() function -- minus 
the Revision part (the fourth set of digits in the version number, after the 
third period), which are always ignored by the Xbase++ OS() function.

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas@AbsoluteSoftwareLLC.com
web:   http://www.AbsoluteSoftwareLLC.com
[F]:   https://www.facebook.com/AbsoluteSoftwareLLC