| title | Hosting a Windows Forms User Control as an MFC View | Microsoft Docs | |||
|---|---|---|---|---|
| ms.custom | ||||
| ms.date | 11/04/2016 | |||
| ms.technology |
|
|||
| ms.topic | conceptual | |||
| dev_langs |
|
|||
| helpviewer_keywords |
|
|||
| ms.assetid | 43c02ab4-1366-434c-a980-0b19326d6ea0 | |||
| author | mikeblome | |||
| ms.author | mblome | |||
| ms.workload |
|
MFC uses the CWinFormsView class to host a Windows Forms user control in an MFC view. MFC Windows Forms views are ActiveX controls. The user control is hosted as a child of the native view and occupies the entire client area of the native view.
The end result resembles the model used by the CFormView Class. This lets you take advantage of the Windows Forms designer and runtime to create rich form-based views.
Because MFC Windows Forms views are ActiveX controls, they do not have the same hwnd as MFC views. Also they cannot be passed as a pointer to a CView view. In general, use .NET Framework methods to work with Windows Forms views and rely less on Win32.
For a sample application that shows Windows Forms used with MFC, see MFC and Windows Forms Integration.
How to: Create the User Control and Host MDI View
How to: Add Command Routing to the Windows Forms Control
How to: Call Properties and Methods of the Windows Forms Control
Using a Windows Form User Control in MFC
How to: Author Composite Controls