I had that problem before too. The way I got around it is I did not let
Clarion manifest the app. I used the free Bo utility to add the resource...
so it's automatically compiled into the app.

Then, I created a separate setupbuilder script to manifest then sign each of
my EXE's... I have a batch file to sign my dll's.

In SB I use the embed UAC Manifest, with skip and permanent checked, then
right after I code sign with skip and permanent checked... do that for each
EXE.

I saw no reason to add a manifest to the dlls.. I just code sign them with
my normal batch file.

Ray
VMT