CHAPTER 19 BUILDING (Web hosting providers) A BETTER WINDOW WITH
CHAPTER 19 BUILDING A BETTER WINDOW WITH SYSTEM.606 STEM.WINDOWS.FORMS Given that the total number of types within System.Windows.Forms is well over 100 strong, it would be redundant (not to mention a terrible waste of paper) to list every member of the Windows Forms family. To set the stage for the next several chapters, however, Table 19-1 lists some of the core .NET 2.0 System.Windows.Forms types (consult the .NET Framework 2.0 SDK documentation for full details). Table 19-1. Core Types of the System.Windows.Forms Namespace Classes Meaning in Life Application This class encapsulates the runtime operation of aWindows Forms application. Button, CheckBox, ComboBox, These classes (in addition to many others) correspond to DateTimePicker, ListBox, various GUI widgets. You ll examine many of these items in LinkLabel, MaskedTextBox, detail in Chapter 21. MonthCalendar, PictureBox, TreeView FlowLayoutPanel, .NET 2.0 now supplies various layout managers that TableLayoutPanel automatically arrange a Form s controls during resizing. Form This type represents amain window, dialog box, or MDI child window of aWindows Forms application. ColorDialog, OpenFileDialog, These are various standard dialog boxes for common GUI SaveFileDialog, FontDialog, operations. PrintPreviewDialog, FolderBrowserDialog Menu, MainMenu, MenuItem, These types are used to build topmost and context- ContextMenu, MenuStrip, sensitive menu systems. The new (.NET 2.0) MenuStrip and ContextMenuStrip, ContextMenuStrip controls allow you to build menus that may contain traditional drop-down menu items as well as other controls (text boxes, combo boxes, and so forth). StatusBar, Splitter, ToolBar, These types are used to adorn a Form with common child ScrollBar, StatusStrip, ToolStrip controls. Note In addition to System.Windows.Forms, the System.Windows.Forms.dll assembly defines additional GUI-centric namespaces. For the most part, these additional types are used internally by the Forms engine and/or the designer tools of Visual Studio 2005. Given this fact, we will keep focused on the core System.Windows.Forms namespace. Working with the Windows Forms Types When you build aWindows Forms application, you may choose to write all the relevant code by hand (using Notepad or TextPad, perhaps) and feed the resulting *.cs files into the C# compiler using the /target:winexe flag. Taking time to build some Windows Forms applications by hand not only is a great learning experience, but also helps you understand the code generated by the various graphics designers found within various .NET IDEs. To make sure you truly understand the basic process of building aWindows Forms application, the initial examples in this chapter will avoid the use of graphics designers. Once you feel comfortable with the process of building aWindows Forms application wizard-free, you will then leverage the various designer tools provided by Visual Studio 2005.
We recommend high quality webhost to host and run your jsp application: christian web host services.