Else, if my application's executable were named "spiff.exe" then my resource manifest file should be named "spiff.exe.Manifest" and reside in the same directory as the executable.
Hope this helps.
PS. For those of you paying attention, the processorArchitecture type should not be "x86" if you want your program to run under Win64. (It won't run at all otherwise.)
To be fair, I had read about this on MSDN. The problem is my attempt failed miserably. I hadn't gotten past the conceiving of the manifest. Thanks for giving a concrete example. There is another problem though...it doesn't work.
Please, load up Resource Hacker and navigate to the resource number 24, click to expand the tree to item 1 and cut and paste the XML data that appears in the right pane so the rest of us can see it.
I've been using the #pragma statement from the get-go and it's never let me down, so I'll see your "curious" and raise you one. -:)
I.e., is there any reason to not use the #pragma as opposed to the XLM coding? Also, when you instructed LolFactor to add it to his resources, do you mean simply paste that code into an RC file, or just have it as a simple text file that is included as a resource file in your project?
@Duoas
Yes, that is another thing I don't get....add the manifest where in my resources. Lamblion has a point.
But you are right, I've seen many applications work with exterior manifests like you suggested. It is not, however, the case with mine.
Edit:
I removed the pragma and tried ResHack and replaced resource 24 with the manifest you provided....although it was already there...word for word. Dunno HOW it was there, but it was. Anyway, it didn't work. Sorry to disappoint, but the pragma is just more practical and easy to use, since it resolves the dependencies automatically.