Dec. 27th, 2007

billroper: (Default)
It turns out that my program isn't working because the ATL COM DLL that the other guys created isn't correctly inserting itself into the DLL chain with the result that none of the MFC resources (like say, our strings DLL) are available to the DLL or any of the DLLs that it's calling into. It seems that I need to invoke a bit of MFC magic to get the thread that contains the CWinApp object to initialize its module state correctly.

Unfortunately, I haven't quite figured out the correct incantation.

I recognize that this is complete mumbo jumbo to most of you; sadly, it appears to have been the same to the rest of our development team or this would already be working.

For the moment, I'm deferring this problem to tomorrow and heading home.
billroper: (Default)
It turns out that my program isn't working because the ATL COM DLL that the other guys created isn't correctly inserting itself into the DLL chain with the result that none of the MFC resources (like say, our strings DLL) are available to the DLL or any of the DLLs that it's calling into. It seems that I need to invoke a bit of MFC magic to get the thread that contains the CWinApp object to initialize its module state correctly.

Unfortunately, I haven't quite figured out the correct incantation.

I recognize that this is complete mumbo jumbo to most of you; sadly, it appears to have been the same to the rest of our development team or this would already be working.

For the moment, I'm deferring this problem to tomorrow and heading home.

Profile

billroper: (Default)
billroper

July 2025

S M T W T F S
   1 2 3 4 5
6 7 8 9 10 1112
13141516171819
20212223242526
2728293031  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 12th, 2025 06:22 pm
Powered by Dreamwidth Studios