This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 1%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
In vs2008， My Project works normally, but when I upgrade to vs201, the global CWinApp object be called twice and occur the error: "ASSERT(AfxGetThread() == NULL); (appcore.cpp)"
I dont know what happen! = _ =!!!
Hi @ShowMeYourCode ,
I downloaded VS2017 and tested CWinApp with the following code, the problem you mentioned did not appear. Could please provide a minimal reproducible example?
#include<afxwin.h>
class CmyFrameWnd :public CFrameWnd
{
};
class CMyWinApp :public CWinApp
{
public:
CMyWinApp()
{
}
virtual BOOL InitInstance()
{
CmyFrameWnd* pFrame = new CmyFrameWnd;
pFrame->Create(NULL, L"sda");
m_pMainWnd = pFrame;
pFrame->ShowWindow(SW_SHOW);
pFrame->UpdateWindow();
return TRUE;
}
};
CMyWinApp theApp;
Thank you for your apply!
I did the same test and works normally.
//********in the header file
class CMyApp: public CWinApp
{
public:
CMyApp();
~CMyApp() { }
virtual BOOL InitInstance();
virtual BOOL OnIdle(LONG ICount);
virtual int ExitInstance();
virtual int Run();
virtual BOOL PumpMessage();
virtual BOOL PreTranslateMessage(MSG* pMsg);
};
//********in the source file
CMyApp theApp; //it will be called twice
CMyApp::CMyApp()
{
}
CMyApp::InitInstance()
{
//register the exception handler function
curl_global_init(CURL_GLOBAL_ALL); //init the curl, rely on curl library
// and so on
}
In my opinion, This error may be related to the upgrade vs version.
Hi @ShowMeYourCode ,
It looks like the problem is not from the code, I suggest you go to DC to report this issue.
Set a breakpoint on the CMyApp constructor. When it is called the second time you should be able to examine the call stack. Hopefully that will assist you in locating the problem. If it is not called twice then set the breakpoint on the MFC CWinApp constructor and try again. And the MFC assertion should give you the option of debugging the code. If you do, you should also be able to examine the call stack at that point.
I have set the breakpoint on the "CMyApp theApp". In vs2017, I cant into the source of CWinApp ctor function.
This the call stack:
OK, Thank you very much.
You need to load symbol files to see a complete call stack.
Go to Debug->Options->Symbols and enable the Microsoft Symbol Server and set a path for the downloaded symbol files. For example,
Then, when your breakpoint is hit you should be able to step into the MFC source code for the CWinApp constructor (give the VS Debugger time to load the various symbol files) and the call stack should look something like this -
Thanks to the patient reply.
My project is in the private network env, cant load symbols.
And I have do the test: Create new project with vs2017 and debug, it can into the mfc source code, but I can't enter it through debugging of my project.
I found that my project rely on mfc140d.dll, I don't know if it has anything to do with this.
You can refer to MFC shared DLL naming conventions for an explanation of how MFC DLLs are named.
If you use the VS2008 MFC new application wizard to create a new project and then build that project using VS2017 does the application execute correctly? If it does, that would indicate that the problem is in your code, not with VS2017 or MFC.
Yes, I also do the same test, and it works normally.
It's really let me feel confused.
I think if the code is wrong, Why does it work in vs2008 version?
Sorry, but without more information its not possible for me to diagnose the problem.
Thank you very much.
It's my mistake =_=