PRB: ClassWizard Doesn't Bring in Proper Header FileLast reviewed: June 26, 1997Article ID: Q155133 |
The information in this article applies to:
SYMPTOMSAfter creating a new class derived from either CSocket or CAsyncSocket using the ClassWizard, one of the following errors occur during compilation:
error C2504: 'CSocket' : base class undefined error C2504: 'CAsyncSocket' : base class undefined CAUSEClassWizard allows you to derive a class directly from CSocket or CAsyncSocket; however, it does not pull in the required header file where these classes are declared. Therefore, the compiler displays an error message reflecting that CSocket or CAsyncSocket was not defined.
RESOLUTIONInclude the header file, afxsock.h, into your project, preferably in your project's StdAfx.h header file:
... #include <afxsock.h> //MFC support for Sockets ... STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONThe header file, afxsock.h, contains the class definitions for CAsyncSocket and CSocket. If you are using these classes or any classes that are derived from these classes, you must make sure to include afxsock.h in your project. Also note that if you use AppWizard to start your project and select the Socket Support option on the fourth page of the wizard, you will automatically get afxsock.h inserted into your StdAfx.h file. In addition, you will get the function call, AfxSocketInit(), inserted into your project. This is very important because you must make a call to AfxSocketInit() if you want to use Sockets in your MFC application. This function is usually called from your InitInstance() method of your CWinApp derived object.
BOOL CMyApp::InitInstance() { if (!AfxSocketInit()) { AfxMessageBox("Socket Initialization Failed"); return FALSE; } ... } |
Keywords : kbprg MfcSockets
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |