Create and configure menus
June 29th, 2007 - by Johan Hiemstra
Covers Exam Objective: 70-526 - Create and configure a MenuStrip component on a Windows Form.
One of the challenges with designing graphical user interfaces is to present the controls and information when the user needs them and at the same time not clutter the interface. Most applications however, include a wide variety of options and functions that need to be within reach at all times. A familiar way to allow users access to common functions in Windows applications is to use menus.
There are many different types of menus being used in today’s software of which several are available as components in the .NET framework. By creating custom controls, extending existing controls, and/or by using GDI+, you can create an endless range of menus that differ in look and functionality. In this article, I will cover the two exam objectives listed above, so in particular the MenuStrip component.
The MenuStrip represents the most common menus in Windows apps – the main menu at the top that often starts with a File menu option. It is derived from the ToolStrip component. Just to make sure we all know up front what we’re talking about, the following image depicts the menu in Visual Studio VB Express edition:

As we all know, most of Microsoft’s own software often includes a huge amount of menu options. There is a good chance the first app(s) you create do not contain that many options and then a MenuStrip may seem like overkill. However, besides being a familiar component for users, it can give the GUI some weight and it can easily be extended because of its hierarchical structure. So if the functionality of your application is likely to expand over time, using a MenuStrip from the start can prevent you from having to make major changes to the GUI.
Covers Exam Objective: 70-526 - Create and configure a MenuStrip component on a Windows Form.
One of the challenges with designing graphical user interfaces is to present the controls and information when the user needs them and at the same time not clutter the interface. Most applications however, include a wide variety of options and functions that need to be within reach at all times. A familiar way to allow users access to common functions in Windows applications is to use menus.
There are many different types of menus being used in today’s software of which several are available as components in the .NET framework. By creating custom controls, extending existing controls, and/or by using GDI+, you can create an endless range of menus that differ in look and functionality. In this article, I will cover the two exam objectives listed above, so in particular the MenuStrip component.
The MenuStrip represents the most common menus in Windows apps – the main menu at the top that often starts with a File menu option. It is derived from the ToolStrip component. Just to make sure we all know up front what we’re talking about, the following image depicts the menu in Visual Studio VB Express edition:

As we all know, most of Microsoft’s own software often includes a huge amount of menu options. There is a good chance the first app(s) you create do not contain that many options and then a MenuStrip may seem like overkill. However, besides being a familiar component for users, it can give the GUI some weight and it can easily be extended because of its hierarchical structure. So if the functionality of your application is likely to expand over time, using a MenuStrip from the start can prevent you from having to make major changes to the GUI.





