Home/ Questions/Q 95711
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T23:42:04+00:00

I’m adding C# WPF dialogs to an existing C++ MFC app, using a C++/CLI

  • 0

I’m adding C# WPF dialogs to an existing C++ MFC app, using a C++/CLI interface layer. I’ve got things working, except I’m having a problem with modality. For example:

  1. MFC app shows a WPF dialog using ShowDialog. Works as expected.
  2. That WPF dialog shows a MFC dialog using DoModal. The WPF dialog is hidden behind the base C++ app, and is not disabled unless I manually change IsEnabled. Not ideal, but it works.
  3. Now, that MFC dialog is closed. Now for some reason the base MFC app is enabled, when it should still be disabled due to the WPF dialog not having been closed. That’s bad, as it now allows the user to do crazy things while the WPF dialog is still open.

I have a feeling that it would work better if I could set parent dialogs correctly. But so far I havent been able to set an MFC dialog’s parent as a WPF dialog, or vice versa. And, I don’t even know if that’d fix it.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. When opening a CDialog, the trick is to use a WindowsInteropHelper to get the parent WPF dialog’s HWND. Then, you can use CWnd::Attach to wrap that HWND in a CWnd class to pass to the CDialog’s constructor.

    The problem I had was that I already had the CDialog constructed., but not yet displayed. The various versions of SetParent can only be used if your target child window already has a valid handle. I had to write a new function in my CDialog class to set m_wndParent, which is what it uses as the parent when it finally creates the dialog. Then everything works great!

    Somehow creating WPF dialogs from MFC dialogs ‘just works’. It’s magic.

    • 0