Makeover Color theme not working after install

[NewsArchive]

Ok, I am posting here because it is after I create the install, which
manifests and code signs my exe that this problem takes place.

I have a program pos.exe. I have lots of other exe's that have no
problem, but this one seems to fail (color-wise) when I either code sign
it or manifest it with setupbuilder. The colors are 'sort of' there.. I
get some white screens instead of blue for instance.

I turned off the code signing... not the manifest, and it still failed.
However if I turned off the manifest, but code signed it, it worked...
so the manifest is causing the problem somehow.

This is an ABC program running c9.1 gold in windows 8.1.

the manifest is 'asinvoker', skip if manifested, Permanent, and I tried
it both with Windows 7 and 8.1 compatibility settings.

Any idea's.

Thanks,

--
Ray Rippey
VMT Software

[NewsArchive]

FWIW - I use the shipping template to generate the manifest. Only the
first check box and the last 3 are not checked in the template dialog.
I let SB code sign the EXE and DLLs as well as the installer/uninstaller
programs.

If you select the MakeOver option to disable the template, does it look
OK then?

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

In Clarion, try this -

Global Properties
Actions
App Settings tab
Application Manifest button

mark the "SHEET controls do not use the OS Theme color" checkbox.

That will probably get rid of the white you're seeing.

jf

[NewsArchive]

Ray,

It has nothing to do with SetupBuilder or your install. Without a manifest
in your pos.exe program, your app loads a completely different version of
ComCtl32.dll (Windows Common Controls). So in your case, the visual styles
of the ComCtl32.dll (enabled by the manifest) cause it.

Friedrich

[NewsArchive]

Friedrich,

in other words, there are two different version of ComCtl32.DLL installed on a
Windows machine, one for programs without a Manifest and a second for programs
with a Manifest?

Wie krank ist das denn?

<mumble_mumble />

Regards,
Wolfgang Orth
www.odata.de

[NewsArchive]

Ok, here's what I did. I did change the pos.exe to not use the OS
colors... but I did not build a manifest in the app.. I let SB do it (as
I always have). That app worked but the procedures it called did not...
so I manifested the dlls with the app settings generate, link, configure
as invoker and turned on the sheet controls do not use os colors.

I never manifested the dlls before as I thought only exe's got
manifested. This made everything work.. so far.

Ray

[NewsArchive]

Ray,

> I never manifested the dlls before as I thought only exe's got manifested.
> This made everything work.. so far.

"asInvoker" is not a valid element in a DLL "manifest" (often referred to as
assembly manifest). So perhaps you have added an assembly manifest that
defines side-by-side assemblies to which your pos.exe application should
bind at run time (e.g. you change the search order for dependency files). I
have no idea what kind of negative side effects this might cause.

BTW, the manifest in the pos.exe executable is what "controls" the visual
styles (theme support).

Friedrich