Is this a bug or OS feature?
Comments: This is legal, look
here<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
<!-- Application supports Windows 10 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
<!-- Application supports Windows 8.1 -->
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
<!-- Application supports Windows 8 -->
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
<!-- Application supports Windows 7 -->
<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
<!-- Application supports Windows Vista -->
<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
</application>
</compatibility>
EDIT:
porc don't have support UNICODE name 'MANIFEST' like MS RC have.
test1 use msvc compiled obj and res with polink
test2 use pocc compiled obj and MS RC compiled res with polinkEDIT:
Save rc-file in format UTF-16LE and name MANIFEST with name MANIFEST.
MANITEST MANIFEST "res1.xml"
With that named manifest can use UTF8 strings?