I make an MFC ActiveX component in Visual C++ 2005 and need to link the C++ runtime and MFC as static libraries to reduce the DLL hell for end users. The problem seems to be that the static library did not implement the methods that existed in the dynamic version of MFC.
I have implemented my own DllCanUnloadNow with a use counter but I can't implement DllGetClassObject because everything in MFC is hidden with many layers of inheritance and thin documentation.
I have access to my own control class inheriting COleControl but I can't find access to the class ID (CLSID m_clsid) or the hidden factory class implementing QueryInterface.
1
Using static MFC library and implementing DllGetClassObject
Started by Dawoodoz, Jun 13 2012 01:51 PM
2 replies to this topic
#1 Members - Reputation: 280
Posted 13 June 2012 - 01:51 PM
My open source DirectX 10/11 graphics engine. https://sites.google.com/site/dawoodoz
"My design pattern is the simplest to understand. Everyone else is just too stupid to understand it."
Ad:
#2 Members - Reputation: 280
Posted 14 June 2012 - 07:30 AM
It seems that the runtime dependency was removed when I selected to use a static MFC so that I removed it twice. Now it is working without dependencies to the MFC or C++ runtime.
Edited by Dawoodoz, 14 June 2012 - 07:58 AM.
My open source DirectX 10/11 graphics engine. https://sites.google.com/site/dawoodoz
"My design pattern is the simplest to understand. Everyone else is just too stupid to understand it."
#3 Members - Reputation: 280
Posted 15 June 2012 - 01:31 PM
Now the dynamic library is back somehow and causing link errors.
Compiling the same code again caused the error to disappear.
Compiling the same code again caused the error to disappear.
Edited by Dawoodoz, 15 June 2012 - 01:34 PM.
My open source DirectX 10/11 graphics engine. https://sites.google.com/site/dawoodoz
"My design pattern is the simplest to understand. Everyone else is just too stupid to understand it."
