The Web has become a gossip topic, and it looks as if Microsoft Visual Studio development system has weakened support for creating legacy applications based on Microsoft Windows. In fact, Microsoft's investment in windows-based application development is increasing.
The Win form is a new form package that enables developers to take full advantage of the rich user interface features offered by Microsoft Windows operating systems to create windows-based applications. Win Forms is an integral part of the new Microsoft. NET platform, providing a wide range of new technologies, including a common application framework, a manageable execution environment, integrated security, and object-oriented design principles. Also, Win Forms fully supports fast and easy access to Web Services and the creation of rich data-aware applications based on ado+ data models. Thanks to the new shared development environment in Visual Studio, developers can create a Win Forms application using any language that supports the. NET platform, including Microsoft Visual Basic and C #.
Introducing Win Forms
As you've just said, Win Forms is a namespace for the. NET Framework that is dedicated to Windows client UI programming. It shares the same design principles as the asp+ UI package, Web Forms, but its classes and implementations are completely different. A class that is not magically deformed between the Microsoft Win32 API and the Web component. As with all. NET frameworks, consistency has become a priority issue. The goal is to Win the forms developer to quickly adapt to writing code in Web forms, and vice versa. For example, all namespaces have Button classes, each with text, default OnClick events, and ForeColor, BackColor, and Font properties.
All of the controls for Win Forms are based on the System.WinForms.Control class. Control has all the basic HWND features built into it, and it handles most of the common wm_xxxx messages we already know and love. Richcontrol is derived from control, where layout logic and drawing code are added. Most of the controls in the System.WinForms namespace are actually derived from Richcontrol. ScrollableControl can support scrolling of window client areas. In general, support for scrolling functions is implemented through ContainerControl, which is derived from ScrollableControl and increases support for managing child controls, focus issues, and hurdles. The form, derived from ContainerControl, is the top-level control of Win Form with properties that control the title bar, system menus, non rectangular windows, and default controls. UserControl, also derived from Containtercontrol, is the basic class of controls that developers can create. UserControl is typically used to host other child controls, but it appears as a single unit for external clients. UserControl and Form at Microsoft? Visual Studio.NET has a visual designer that you can find to add and design the items that are derived from the class.