Question

I have a class library which is called through COM from a Third Party RAD application (Omnis Studio), the library provides .NET functionality such as a SQL/Web Service bridge. I’ve had to add further methods to display a WPF form which fires events back to the original application.

This all works fine, the project has to be a class library and could not be an executable which meant that I cannot select a manifest for the project in the Application Options Tab. The main problem I have now is that without the piece of XML below in my manifest file I cannot get the modern windows dialog buttons so the buttons in message boxes look somewhat antiquated.

<!-- Enable themes for Windows common controls and dialogs (Windows XP and later) -->

<dependentAssembly>
  <assemblyIdentity
      type="win32"
      name="Microsoft.Windows.Common-Controls"
      version="6.0.0.0"
      processorArchitecture="*"
      publicKeyToken="6595b64144ccf1df"
      language="*"
    />
</dependentAssembly>

So is there a way that I can achieve the same effect from having those lines in the manifest file but performed by bespoke code in an entry point into the class library?

Thanks

Paul

EDIT

To add clarification for Rahmound’s comment:

I don’t think you understood the question. Firstly I made no mention of this being a Windows Form application, there are zero Windows Forms assembly references in the project, only WPF presentation assemblies. The project has to be a class library as the THIRD party application (which is a C++ unmanaged application) can only consume .NET class libraries, there was a need to display a very custom form, this could be achieved in the current project and I chose WPF because that’s where most of my desktop app skills lie and it suited WPF’s databinding model. We are very pleased with the end result, the only issue I have is with my application needing to use XP+ themed Windows controls, if that section above is not in the app.manifest then instead message boxes use the old style OK, Cancel buttons which is not in keeping with all other buttons I have in my application.

This question explains the message box problem

What I need is to be able to achieve the same thing but without having the embedded app.manifest.

Answer 1

I couldn’t solve this and time was running out, following on from Hans suggestion I ended up using the Extended WPF Toolkit as I also wanted to use other controls such as the ColourPicker.