Hi Lee,
> I know you can specify a version resource for the install but I'd also
> like to embed a version resource in other files using something along
> the lines of "#embed version resource" in the same manner I already
> use "#embed UAC manifest" and "#code-sign application".
Huh? You been looking inside my computer while I'm on the Internet? <g>
The problem is that this is not a trivial task at all. To manipulate the
version resource of an application file, you have to "re-create" the whole
PE structure, update the checksum, etc. This is a very complex and
failure-prone process. And it still might result in fatal application
failures. Over the years, I have tried freeware and commercial tools and
quite often it damaged the .EXE and .DLL files. The encoding (Unicode and
non-Unicode) makes a big difference and the original compiler that created
the application.
But hey, you already had this very good idea five years ago <g>
http://www.lindersoft.com/forums/showthread.php?27221
But I think that I have a somewhat stable "#edit version resource..."
compiler directive now. And I bet that Antivirus and anti-spyware
"protection" systems will love this feature <g>. To be on the safe side,
I'll mark it as a "use at your own risk" function <g>
See attached screenshots. I'll enable this directive in the next SB build.
Thank you for your suggestion.
> By the way, Friedrich, thanks for fixing the code sign dialog so it
> doesn't forget the descriptive name when selecting a different
> certificate profile.
You are very welcome
Friedrich