There's an old VC6 procedure, upgraded to vs2010, run OK, ready to put the CMDIChildWnd into CMDIChildWndEx inside these days, CWinApp CWinAppEx, CMDIFrameWnd CMDIFrameWndEx, change some errors in addition to the back,

But in xxxxApp: : InitInstance (), in the LoadFrame function not success! Always enter the return FALSE;

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
CMainFrame * pMainFrame=new CMainFrame;

if(! PMainFrame - & gt; LoadFrame
(IDR_MAINFRAME)){
return FALSE.
}

M_pMainWnd=pMainFrame;
CMyCommandLineInfo cmdInfo;
ParseCommandLine (cmdInfo);
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Have encountered similar problems?? Consult the great god,

CodePudding user response:

In the if (! PMainFrame - & gt; LoadFrame IDR_MAINFRAME) set a breakpoint, single step tracking check, concrete is which step out of the question

CodePudding user response:

One step in LoadFrame? Can't enter, API can't debugging,

CodePudding user response:

You have tried? It belongs to the category of MFC

CodePudding user response:

Is there some initialization have change

CodePudding user response:

VS2010 add a VC6 procedures the same with you, and then check xxxxApp: : InitInstance () the difference of the code, Vs2008 SP1 and after running the initialization code and VC6 running there will be some difference

CodePudding user response:

Step in and see what is problem