PDA

View Full Version : #embed UAC manifest



NewsArchive
11-15-2016, 02:32 AM
Where can I file the ProgramName.exe.manifest file after using the
#embed UAC manifest function?


--
Darrel (Dee) Witham
Professional Data Services, Inc

NewsArchive
11-15-2016, 02:32 AM
Hi Darrel,

It'll be 'embedded' in the EXE file (unless you specifically have, and
use, an option to generate it as external).

If you open the EXE in a HEX editor the manifest is usually found near
the end, just look for embedded XML stuff.

Graham

NewsArchive
11-15-2016, 02:33 AM
Hi Darrel,

See attached for example of an embedded manifest in Notepad.exe
In this case it was about half way within the EXE :-)

You can search for the XML start <? xml version = "1.0" string.

Graham

NewsArchive
11-15-2016, 02:39 AM
Graham - thanks

--
Darrel (Dee) Witham
Professional Data Services, Inc

NewsArchive
11-19-2016, 02:31 AM
Graham - I am using SetupBuilder to code sign our product. I compile
all dlls and exes then code sign. Should I code sign before or after
using SetupBuilder to create the UAC manifest? I am assuming I manifest
after re-compile.

TIA

--
Darrel (Dee) Witham
Professional Data Services, Inc

NewsArchive
11-19-2016, 02:31 AM
> I am using SetupBuilder to code sign our product. I compile
> all dlls and exes then code sign. Should I code sign before or after
> using SetupBuilder to create the UAC manifest? I am assuming I manifest
> after re-compile.

Dee,

Your code signing is done after the manifest is embedded.

Think of it as putting a pretty ribbon around the file. The ribbon being
intact means the file is Ok, but adding the manifest after the code sign
would mean that the ribbon had to be cut to add it (thus invalidating the
code signing).

We use external manifest files in the test directory during development.
This means you can "compile and run" and see the manifested results during
development without needing Clarion to embed the manifest file.

Then as the installer is built, we have two lines in the SetupBuilder
script to add the embedded manifest, then to code sign the file.

That makes sure that you are always getting the best effort for a correctly
manifested and code signed file since SetupBuilder is always up to date on
what needs to be done (just be sure and keep your SetupBuilder subscription
current and the product up to date).

Does that help?

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

cjeByteMeSpammers@lansrad.com (remove the "ByteMeSpammers" to email me)
www.clarionproseries.com - ProScan, ProImage, ProPath and other Clarion
developer tools!
www.solidsoftware.de - ImageEx and RichReport templates!
www.seal-soft.com - The xProduct Clarion templates - xWordCOM, xToolTip,
xDataBackup Manager and more!
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms - Now with PNG support!
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

NewsArchive
11-19-2016, 02:32 AM
Hi Dee,

what Charles said. Embed the manifest and after that code-sign. The other
way around would "break" the code-signature (because embedding a manifest
changes the binary contents of the file).

Friedrich

NewsArchive
11-19-2016, 02:33 AM
Thanks all!

--
Darrel (Dee) Witham
Professional Data Services, Inc