How is the Windows form application development supported in .NET?

Most of the library classes for Windows form application development are present in .NET framework’s System.Windows.Forms namespace. All the forms in .Net are represented by sub-classes of System.Windows.Forms.Form class. To make a form, we need to inherit our form class from the System.Windows.Forms.Form class.

A form may contain various user interface (UI) controls. All the controls, in .NET, are represented by subclasses of System.Windows.Forms.Control class. Each form has a collection (named ‘Controls’) to store the constituent controls of the form. In fact, a form itself is a special type of control called Container Control, i.e., the Form class itself is derived from the ContainerControl class which is a subclass of the Control class. A container control, as the name suggests, may contain other controls. Other examples of the Container control include Panel and Tab Control.

Each control, and thus form, exposes a number of events that can be triggered on certain user action or application behavior. For example, a button raises Click event whenever it is clicked and the text box raises the TextChanged event whenever its text is changed. The application developer can write even handler to catch these events and perform corresponding action. Beside these, a form also has certain set of events called the form life cycle events. These events are triggered during the life cycle of form to indicate the current state of the form.

Index

 

Advertisement

Free Magazine