Commit 116fbda

Because [CWinFormsView::GetControl](../mfc/reference/cwinformsview-class.md#cwinformsview__getcontrol) returns a pointer to <xref:System.Windows.Forms.Control?displayProperty=fullName>, and not a pointer to `WindowsControlLibrary1::UserControl1`, it is advisable to add a member of the user control type and initialize it in [IView::OnInitialUpdate](.../mfc/reference/iview-interface.md#iview__oninitialupdate). Now you can call methods and properties using `m_ViewControl`.

[DDX_ManagedControl](http://msdn.microsoft.com/Library/61b55a90-c993-478e-9dea-db27fbf0e193) calls [CWinFormsControl::CreateManagedControl](../mfc/reference/cwinformscontrol-class.md#cwinformscontrol__createmanagedcontrol) to create a control matching the resource control ID. If you use `DDX_ManagedControl` for a `CWinFormsControl` control (in wizard-generated code), you should not call `CreateManagedControl` explicitly for the same control.

Call `DDX_ManagedControl` in [CWnd::DoDataExchange](../mfc/reference/cwnd-class.md#cwnd__dodataexchange) to create controls from resource IDs. For data exchange, you do not need to use the DDX/DDV functions with Windows Forms controls. Instead, you can place code to access the properties of the managed control in the `DoDataExchange` method of your dialog (or view) class, as in the following example.

The control is created when [CDialog::OnInitDialog](../mfc/reference/cdialog-class.md#cdialog__oninitdialog) calls `CMyDlg::DoDataExchange` for the first time, so any code that references `m_UserControl` must come after the `DDX_ManagedControl` call.

[CWnd::DoDataExchange](../mfc/reference/cwnd-class.md#cwnd__dodataexchange)

- Your code may query types at runtime with [CRuntimeClass::FromName](../mfc/reference/cruntimeclass-structure.md#cruntimeclass__fromname). However, if a type is in an MSIL .dll (compiled with **/clr**), the call to `FromName` may fail if it occurs before the static constructors run in the managed .dll (you will not see this problem if the FromName call happens after code has executed in the managed .dll). To work around this problem, you can force the construction of the managed static constructor by defining a function in the managed .dll, exporting it, and invoking it from the native MFC application. For example:

A pointer to the data type of the Windows Forms user control. For more information, see <xref:System.TypequalifyHint%3DTrue%26autoUpgrade%3DTrue>.

This example shows how to provide a custom compare function. It uses the [std::complex::real](../../standard-library/complex-class.md#complex__real) method to sort [std::complex\<double>](../../standard-library/complex-double.md) values in ascending order.

|[ExitInstance](../mfc/reference/cwinthread-class.md#cwinthread__exitinstance)|Perform cleanup when thread terminates. Usually overridden.|

|[InitInstance](../mfc/reference/cwinthread-class.md#cwinthread__initinstance)|Perform thread instance initialization. Must be overridden.|

|[OnIdle](../mfc/reference/cwinthread-class.md#cwinthread__onidle)|Perform thread-specific idle-time processing. Not usually overridden.|

|[PreTranslateMessage](../mfc/reference/cwinthread-class.md#cwinthread__pretranslatemessage)|Filter messages before they are dispatched to **TranslateMessage** and **DispatchMessage**. Not usually overridden.|

|[ProcessWndProcException](../mfc/reference/cwinthread-class.md#cwinthread__processwndprocexception)|Intercept unhandled exceptions thrown by the thread's message and command handlers. Not usually overridden.|

|[Run](../mfc/reference/cwinthread-class.md#cwinthread__run)|Controlling function for the thread. Contains the message pump. Rarely overridden.|

`AfxBeginThread` does most of the work for you. It creates a new object of your class, initializes it with the information you supply, and calls [CWinThread::CreateThread](../mfc/reference/cwinthread-class.md#cwinthread__createthread) to start executing the thread. Checks are made throughout the procedure to make sure all objects are deallocated properly should any part of the creation fail.

- Store the thread's handle separately. After the thread is created, copy its `m_hThread` data member (using **::DuplicateHandle**) to another variable and access it through that variable. This way the object is deleted automatically when termination occurs and you can still find out why the thread terminated. Be careful that the thread does not terminate before you can duplicate the handle. The safest way to do this is to pass **CREATE_SUSPENDED** to [AfxBeginThread](http://msdn.microsoft.com/library/e9e8684d-24f7-4599-8fdf-1f4f560a753b), store the handle, and then resume the thread by calling [ResumeThread](../topic/../mfc/reference/cwinthread-class.md#cwinthread__resumethread).

This functionality is intended to let you use controls other than those supplied by Windows. At run time, the control is associated with a window class (not the same as a C++ class). A more common way to accomplish the same task is to install any control, such as a static control, in your dialog box. Then at run time, in the [OnInitDialog](../mfc/reference/cdialog-class.md#cdialog__oninitdialog) function, remove that control and replace it with your own custom control.