About Web Services and C++ on Windows platform : MFC

How to fix "Cannot add event handler because code element marked as read-only" in VS2005 and VS2008

NikolaD — Tue, 09 Sep 2008 06:34:00 GMT

Today VS2008 SP1 pop up an error dialog when I was editing MFC dialog box in VS2008 SP1. The error was saying something like "Cannot add event handler because code element CMainDlg marked as read-only". Clearly neither .cpp nor .h file for this class...(read more)

Aero Wizards (Windows Vista style wizards) in MFC8 (VS2005)

NikolaD — Tue, 11 Jul 2006 04:13:00 GMT

Existing wizards built in MFC can be modified so that appear as Aero Wizards on Windows Vista. Here is a small demo that shows changes required to be done to wizard-generated MFC property sheet and property pages. ...(read more)

Applocal deployment of MFC localized resource DLLs

NikolaD — Tue, 25 Apr 2006 03:28:00 GMT

It was pointed out to me that it is not clear from Docs how to redistribute MFC localized DLLs with MFC application in application local folder. This post contains short example of application local deployment of MFC localized resource DLLs. ...(read more)

Complete example for MFC/Winforms integration

NikolaD — Tue, 19 Jul 2005 23:17:00 GMT

Just posted on MSDN a sample of MFC/Windows Forms integration as it is in Visual Studio 2005. Please be advised that some parts of it may not work with early builds of VS2005. However it should all work on release of VS2005. Here is the link

http://www.microsoft.com/downloads/details.aspx?FamilyID=987021bc-e575-4fe3-baa9-15aa50b0f599&displaylang=en

cannot access private member error when porting MFC project

NikolaD — Thu, 16 Jun 2005 09:44:00 GMT

On the forum, we have surfaced another error. I had a chance today to see a real-world code with this error and actually to narrow down the problem. So if you see an error like

1>c:\program files\microsoft visual studio 8\vc\atlmfc\include\afxwin.h(259) : error C2248: 'CObject::operator =' : cannot access private member declared in class 'CObject'

1> c:\program files\microsoft visual studio 8\vc\atlmfc\include\afx.h(540) : see declaration of 'CObject::operator ='

1> c:\program files\microsoft visual studio 8\vc\atlmfc\include\afx.h(510) : see declaration of 'CObject'

1> This diagnostic occurred in the compiler generated function 'CGdiObject &CGdiObject::operator =(const CGdiObject &)'

The cause of this error is that you are have a class like

class CReproClass {

public:

CReproClass::CReproClass(void) {}

CReproClass::~CReproClass(void) {}

CPen m_pen; //or any other class that subclasses CGdiObject

};

class CReproClass : public CPen{

...
};

then is later used in

CReproClass a;
CReproClass b;
a = b;

This is the cause of the problem.

How to use CWinFormDialog&amp;lt;&amp;gt; for MFC/WinForms Integration

NikolaD — Fri, 10 Jun 2005 07:05:00 GMT

We have had some internal discussion about CWinFormsDialog<> template that clearly discovered some confusion about what is a proper way for user to use this template. In short, this template should be seen as CDialog MFC class. The primary scenario we have in mind for this template is when a developer creates a MFC wrapper around System::Windows::Form::Control for its future use in MFC applications. In other words, let's say you have a Winform control created in either in C++ or C# called HostedWinFormsControl and you want to integrate it with your existing MFC applications. Do this:

- Add #include <afxwinforms.h> to stdafx.h.

- Generate using Class wizard an MFC class that subclasses CDialog. You won't need resource template, so go ahead and delete it. Let's call this new class as CHostForWinForm.

- Go ahead and replace every appearance of CDialog in hostforwinform.h and hostforwinform.cpp with CWinFormsDialog<HostedWinFormsControl>.

- Now you want your MFC dialog listen to events on your winform, for example, you want to know when user clicks on a specific button. You need to add a delegate map, MAP_DELEGATE_MAP, see below. This creates a proxy around your native class that is used to call methods of a native class when a managed event is fired.

- Of course, you need to add OnButtonX() methods to your MFC class that are used as a handlers for Click events on winform side.

- Last step is to organize data exchange, which is basically means to change DoDataExchange() method of the host MFC class as it is shown below.

And that's it. Now you can use this MFC class that hosts Winform as a regular MFC dialog. Here are the code snippets:

--------------------------------------------------------------------------------------------------------

HostForWinForm.h

--------------------------------------------------------------------------------------------------------

#pragma once

// CHostForWinForm dialog

class CHostForWinForm : public CWinFormsDialog<HostedWinForms::HostedWinFormsControl>

// public CDialog

{

DECLARE_DYNAMIC(CHostForWinForm)

public:

CHostForWinForm(CWnd* pParent = NULL); // standard constructor

virtual ~CHostForWinForm();

virtual BOOL OnInitDialog();

// Dialog Data

// enum { IDD = IDD_HOSTFORWINFORM };

protected:

virtual void DoDataExchange(CDataExchange* pDX); // DDX/DDV support

DECLARE_MESSAGE_MAP()

/////////////////////////////////////////////

// CODE YOU ADD TO INTEGRATE WINFORM CONTROL

public:

virtual void OnButton1( System::Object^ sender, System::EventArgs^ e );

virtual void OnButton2( System::Object^ sender, System::EventArgs^ e );

BEGIN_DELEGATE_MAP( CHostForWinForm )

EVENT_DELEGATE_ENTRY( OnButton1, System::Object^, System::EventArgs^ );

EVENT_DELEGATE_ENTRY( OnButton2, System::Object^, System::EventArgs^ );

END_DELEGATE_MAP()

CString m_sEditBoxOnWinForm;

};

--------------------------------------------------------------------------------------------------------

HostForWinForm.cpp

--------------------------------------------------------------------------------------------------------

#include "stdafx.h"

#include "HostForWinForm.h"

// CHostForWinForm dialog

IMPLEMENT_DYNAMIC(CHostForWinForm, CWinFormsDialog<HostedWinFormsControl>)

CHostForWinForm::CHostForWinForm(CWnd* pParent /*=NULL*/)

: CWinFormsDialog<HostedWinFormsControl>(CHostForWinForm::IDD, pParent)

{

}

CHostForWinForm::~CHostForWinForm()

{

}

void CHostForWinForm::DoDataExchange(CDataExchange* pDX)

{

CDialog::DoDataExchange(pDX);

/////////////////////////////////////////////

// CODE YOU ADD TO INTEGRATE WINFORM CONTROL

if (pDX->m_bSaveAndValidate)

m_sEditBoxOnWinForm = CString( m_control->textBox1->Text);

else {

m_pControl->textBox1->Text = gcnew System::String(m_sEditBoxOnWinForm);

}

BEGIN_MESSAGE_MAP(CHostForWinForm, CWinFormsDialog<HostedWinFormsControl>)

END_MESSAGE_MAP()

BOOL CHostForWinForm::OnInitDialog()

{

CWinFormsDialog<HostedWinFormsControl>::OnInitDialog();

/////////////////////////////////////////////

// CODE YOU ADD TO INTEGRATE WINFORM CONTROL

GetControl()->OkButton->Click += MAKE_DELEGATE( System::EventHandler, OnButton1);

GetControl()->CancelButton->Click += MAKE_DELEGATE( System::EventHandler, OnButton2);

return TRUE;

}

/////////////////////////////////////////////

// CODE YOU ADD TO INTEGRATE WINFORM CONTROL

void CHostForWinForm::OnButton1( System::Object^ , System::EventArgs^ )

{

CDialog::OnOK(); // This will close the dialog and DoModal will return.

}

/////////////////////////////////////////////

// CODE YOU ADD TO INTEGRATE WINFORM CONTROL

void CHostForWinForm::OnButton2( System::Object^ , System::EventArgs^ )

{

CDialog::OnCancel(); // This will close the dialog and DoModal will return.

}

Questions, comments, suggestions? Feel free to comment.

P.S.: This code snippet may not work with Beta 2, because we have fixed some bugs in CWinformDialog<> after Beta 2. But this is how it should work in the final release of VS2005.

About Web Services and C++ on Windows platform : MFC

How to fix "Cannot add event handler because code element marked as read-only" in VS2005 and VS2008

Aero Wizards (Windows Vista style wizards) in MFC8 (VS2005)

Applocal deployment of MFC localized resource DLLs

Complete example for MFC/Winforms integration

cannot access private member error when porting MFC project

How to use CWinFormDialog&amp;amp;lt;&amp;amp;gt; for MFC/WinForms Integration

How to use CWinFormDialog&lt;&gt; for MFC/WinForms Integration