Automation server and Windows Themes

[Joe @ WDPS]

I have an interactive MFC VC++ windows app that also acts as an automation
server. It can be run either manually or by invoking a client app using
CreateObject. I'm trying to understand the difference to the application of
being invoked in either of those two ways.

The problem I'm seeing is that dynamically created dialogs do not render
with the Windows theme if the app is started automatically via a COM client.
The main window looks ok, but no pop-up dialogs that occur following startup
are themed. If the program is run manually then all is ok, including if a
COM client subsequently attaches to it.

Anyone have an idea what could be causing this issue? Thanks.

Joe Mattioni
WDPS Software

[Joe @ WDPS]

Found it! The issue is with the manifest used for side-by-side assemblies to
get the correct common controls dll for handling themes. I have had this
manifest as an external file without apparent issue until discovering this
problem with automation. If the app is started by an automation client it
appears that the manifest MUST be embedded in the EXE. That fixed my
problem.

Joe Mattioni
WDPS Software

"Joe @ WDPS" <j...@wdpsoftware.com> wrote in message
news:eUvpR6Dq...@TK2MSFTNGP05.phx.gbl...