EDN Admin
Well-known member
We are integrating our application (a mixed COM and .NET application) into an existing MFC application. Our components (DLLs) are loaded by the MFC application at runtime dynamically using inversion of control and they end up displaying .NET Modeless Dialogs. Tabs and Accelerators do not work on these dialogs.
Prior to this integration, our application was a VB6 application that loads components using a configuration DB and the inversion of control pattern. The loaded components could be VB6, C++, or .NET. In the early days, we had this same tab and accelerator issue on our VB6 application, but Microsoft made a hotfix/roll up that addressed this issue for us:
Any help is appreciated.
Thanks,
Brian R.
View the full article
Prior to this integration, our application was a VB6 application that loads components using a configuration DB and the inversion of control pattern. The loaded components could be VB6, C++, or .NET. In the early days, we had this same tab and accelerator issue on our VB6 application, but Microsoft made a hotfix/roll up that addressed this issue for us:
- Original Roll up Fix for .NET 1.1 - http://support.microsoft.com/kb/887540
- Specific Fix that addressed our issue on 1.1 - http://support.microsoft.com/kb/885446
- .NET 2.0 Merge from .NET FW 1.1 - http://support.microsoft.com/kb/925369/en-us
- What would the path be to request that Microsoft make the same System.Windows.Forms change for us that applies to MFC/C++ as well?
- In the meantime, is it possible to get a copy of the code that MS made in these previous patches? The reason I ask is because implementing IsDialogMessage in a WM_GETMESSAGE Hook is practically useless. MSs impl went way beyond that fix.
Any help is appreciated.
Thanks,
Brian R.
View the full article