Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →In a Visual Basic Windows Forms application, a control is a user-interface component placed on a form to display information, accept input, or let the user take an action. A label, text box, check box, button, and data grid are all examples. In this context, “control” describes a UI component—not a special Visual Basic keyword.
What a control does on a form
A Windows Form is the visual surface of an application; controls are the components arranged on it to build the interface. For example, a form might use labels to identify fields, text boxes to collect information, and a button to start an operation. Microsoft describes a Windows Forms control as “a discrete user interface (UI) element that displays data or accepts data input.” Microsoft Learn’s Visual Basic Windows Forms overview explains the relationship between forms, controls, and responding to user actions.
Examples of common Visual Basic controls
Controls have different purposes. Choose one according to the information the interface must show or the choice or action it must support.
| Control | Typical purpose |
|---|---|
| Label | Displays explanatory or read-only text. |
| TextBox | Accepts or displays text. |
| CheckBox | Lets the user turn an option on or off. |
| Button | Lets the user initiate an action. |
| DataGridView | Displays data in a customizable table. |
Microsoft groups Windows Forms controls by tasks such as displaying data, setting values, grouping interface elements, and providing help. Its catalog also notes replacements for some superseded controls, so a historical example is not automatically the best choice for a new interface. See Controls by Function – Windows Forms.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
How controls are added and respond to users
In Visual Studio, a developer can place controls on a form with the Forms Designer or create and manage them in code. Controls can respond to user actions through events: for instance, clicking a button can raise an event that application code handles. This event-based pattern connects what the user does in the interface to what the program does next. Microsoft’s Windows Forms controls overview covers controls as reusable UI components and their use in applications.
How the term differs from a Visual Basic keyword
A Windows Forms control is implemented as a .NET class. The System.Windows.Forms.Control class is the base class for components with a visual representation; the cited API page is specifically the .NET Framework 4.7.2 reference view. Microsoft’s Control Class reference describes that API. This distinction matters: Visual Basic is the programming language, while the control is an object in the UI framework used by an application.
Windows Forms controls versus native Windows controls
“Control” can also refer to a native Win32 concept. Microsoft’s Win32 documentation describes Windows controls as child windows used with another window for user interaction. That is related to, but not interchangeable with, the .NET Windows Forms Control class. Windows Controls – Win32 apps explains the native-platform usage.
The examples here concern Visual Basic applications using Windows Forms. They do not establish a support or lifecycle recommendation for a particular .NET version or project.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
