From: Jeremy W. <jez...@ho...> - 2009-04-22 22:00:27
|
> On Wed, 22 Apr 2009, Rob May wrote: >> 2009/4/22 Jeremy White <jez...@ho...>: >>> I vote for adding the XP style request directly to perl.exe - in >>> almost all cases it's the "correct" thing to do and is easy enough >>> to remove (and indeed from PerlApp) should you need to. It's also >>> backward compatible so it wont harm Win 2000 users etc. >> What exactly is the "easy" way to remove the new style common controls > from an app that requests them in an embedded MANIFEST? On XP itself > you can provide an external perl.exe.manifest that would override the > embedded one, but on 2003, Vista, 2008 the embedded one always takes > precedence. So you'll need to actually remove the embedded manifest > with a tool like mt.exe, but that is only available as part of the > Windows Platform SDK, so I would not really call it "trivial". As part of my build process I use reshacker (a free utility with a command line interface) to replace the manifest that is added with PerlApp: http://angusj.com/resourcehacker/ I think the perl module below can also replace/delete the manifest (although I haven't tried - on my todo list) http://search.cpan.org/~smueller/Win32-Exe-0.11/lib/Win32/Exe.pm As a side reshacker can also be used to add other resources to exe's (such as icons, bitmaps and string tables) and Win32::GUI automatically picks them up. Cheers, jez. _________________________________________________________________ Share your photos with Windows Live Photos – Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/ |