#embed Vista manifest

[NewsArchive]

Friedrich,

I have a question/suggestion about #embed Vista manifest. I see this
information in the help...

----
Use this function only on application files that do not have an
embedded manifest! For example, make sure the "Include Default XP
Manifest" App Settings option in your Clarion 6 Environment is turned
off. And don't add a manifest to your VS2003, VS2005, etc. projects.
-----

I would like to have this on in my C6 app's global options during the
compile/test phase so that I can see the actual appearance of the
final product. Turning it off to compile for an new installer build
seems time consuming and very easy to forget.

I guess my question/suggestion is this: Is there anyway you could
optionally replace the XP manifest if it exists during the installer
compile to avoid the issues I mentioned above?

Thanks!
Kelly E Major

[NewsArchive]

> I would like to have this on in my C6 app's global options during the
> compile/test phase so that I can see the actual appearance of the
> final product. Turning it off to compile for an new installer build
> seems time consuming and very easy to forget.

Kelly,

Off the top of my head - I think an easy answer is to place an external
manifest file in the folder where your EXE is ran during compile/test.

The file would be like:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="CompanyName.ProductName.YourApplication"
type="win32"
/>
<description>Your application description here.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>


Then you save it as: Application.exe.manifest


When you run the app - the external manifest should be picked up by XP and
the theme applied.

This way you can leave the one in Clarion turned OFF and let SetupBuilder
apply it during a build of the installer.

HTH,

Charles


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

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Charles,

Good thinking! Why didn't I think of that? :)

I'd still like to see what Friedrich thinks about the replacement
option as a member of the LPS I feel this would be the easiest
solution for me. :)

Thanks!!!
Kelly E Major

[NewsArchive]

Kelly,

It's not possible to "replace" the XP manifest and then add the Vista-aware
manifest.

Two possible solutions:

1) Exactly what Charles said :)

-or-

2) Create a dummy "Blank Script" with SetupBuilder and just add the two
"#embed Vista Manifest" and "#code-sign application" compiler functions.
Enable the "Permanent" option. If you "compile" the script, SetupBuilder
manipulates your original .exe and you have a Vista-aware, code-signed
application executable.

If you do 2) and you plan to add that manipulated application file to your
real installer, please remove the "#embed Vista Manifest" and "#code-sign
application" compiler functions from your "main" script.

Does this help?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Friedrich,

>Does this help?

As always.. of course. I'm still annoyed for not thinking of Charles
suggestion myself. :)

Thanks!
Kelly E Major