Re: Theming not working in DLL

Hi Jeffrey

Thanks for your reply.

I have managed to resolve the issue. For reasons that I am still unsure of,
the "#pragma comment" method of specifying Common Controls 6 was not
inserting the relevant code into my manifest file for my non-ATL DLL. I have
inserted the code by hand into the manifest and it all seems to work OK now.

Thanks again for you help.

Best Regards
Mark


""Jeffrey Tan[MSFT]"" <jetan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:q8d6t%23miIHA.4200@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Mark,

If that are not getting the themed appearance in the message box then we
maight not manage the activation context correctly. I guess the first
question is whether or not an activation context is being created. Does
the
call to CreateActCtx succeed? I think we may use windbg to dump the return
value of the CreateActCtx like this:
bp kernel32!CreateActCtxW "gu; r eax;gc"

If the output is INVALID_HANDLE_VALUE(0xFFFFFFFF), it may indicate the
activation context failure.

Also, the resource ID for a manifest in a DLL (2) is typically different
than the resource ID in an executable (1). I would suggest checking to see
what resource ID the /manifestdependency linker uses when creating the
manifest resource.

This is probably not related to your problem, but use
processorArchitecture='*' instead of processorArchitecture=' x86'.

Finally, is it possible for you to provide a little sample project(without
ATL dependency) demonstrating this problem? If I can reproduce this
problem
locally, it is more convenient for us to troubleshoot. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.




.

Relevant Pages

  • RE: ASP.Net timeouts
    ... There's no managed call stack on the thread that throws this exception. ... Microsoft Online Support ... You can send feedback directly to my manager at: ... nature are best handled working with a dedicated Microsoft Support Engineer ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Why does this XPath not work
    ... Regarding on the error "Namespace manager or XsltContext needed." ... components only implemented XPATH 1.0 and XSLT 1.0 function set, ... Microsoft MSDN Online Support Lead ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.xml)
  • RE: Linking Mixed Mode and Managed Assemblies
    ... public void f ... Microsoft Online Community Support ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.vc)
  • RE: Web Administration Tool Crashes when creating user
    ... It will check if the Role Manager has been enabled. ... It is reusing the default connection string name: ... Microsoft Online Community Support ... nature are best handled working with a dedicated Microsoft Support Engineer ...
    (microsoft.public.vsnet.setup)
  • RE: Fix 954345 does not resolve problem for VS 2008 SP1
    ... My name is Hongye and it ... Microsoft Online Community Support ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.general)
Loading