Tuesday, August 20, 2013

Threaded multi chat room server source code in c++ with MFC Part - 2


 we will now demonstrate about the class Server.cpp .

This class is the start point of the server project. It is basically used to call the MFC instance.

There will be some preview of the class here as MFC is out of scope  at the moment --

BOOL CServerApp::InitInstance()
    // InitCommonControlsEx() is required on Windows XP if an application
    // manifest specifies use of ComCtl32.dll version 6 or later to enable
    // visual styles.  Otherwise, any window creation will fail.
    InitCtrls.dwSize = sizeof(InitCtrls);
    // Set this to include all the common control classes you want to use
    // in your application.
    InitCtrls.dwICC = ICC_WIN95_CLASSES;



    // Create the shell manager, in case the dialog contains
    // any shell tree view or shell list view controls.
    CShellManager *pShellManager = new CShellManager;

    // Standard initialization
    // If you are not using these features and wish to reduce the size
    // of your final executable, you should remove from the following
    // the specific initialization routines you do not need
    // Change the registry key under which our settings are stored
    // TODO: You should modify this string to be something appropriate
    // such as the name of your company or organization
    SetRegistryKey(_T("Local AppWizard-Generated Applications"));

    CServerDlg dlg;
    m_pMainWnd = &dlg;
    INT_PTR nResponse = dlg.DoModal();
    if (nResponse == IDOK)
        // TODO: Place code here to handle when the dialog is
        //  dismissed with OK
    else if (nResponse == IDCANCEL)
        // TODO: Place code here to handle when the dialog is
        //  dismissed with Cancel

    // Delete the shell manager created above.
    if (pShellManager != NULL)
        delete pShellManager;

    // Since the dialog has been closed, return FALSE so that we exit the
    //  application, rather than start the application's message pump.
    return FALSE;

PREVIOUS                                                                                                                                    NEXT

No comments:

Post a Comment