The .NET Framework Class Library
All platform services are exposed through the .NET Framework Class Library. So whether you want to make a window appear, read a file, open a network connection, parse an XML document, or use any of the other myriad features of the platform, you will do so by using one or more classes in the class library.
The class library is divided up into
namespaces
. For each area of the API, there is
an appropriate namespace, e.g., XML services are provided by the
System.Xml namespace, GUI services are provided by
the
System.Windows.Forms
namespace, and graphical services are provided by the
System.Drawing namespace. Namespaces are
hierarchical, and large namespaces are frequently subdivided into
several smaller namespaces, e.g., the design-time parts of the
Windows Forms API appear in the
System.Windows.Forms.Design namespace.
Because the Class Library replaces large amounts of the Win32 API,
and also adds new functionality not previously available, it is large
and contains many namespaces. This book concentrates on the Windows
Forms namespace, and the related System.Drawing
namespace, although we will discuss other relevant classes as
necessary.
Windows Forms and GDI+
Windows
Forms is the name given to the parts of the .NET Framework Class
Libraries used for building rich client
applications, i.e., traditional GUI applications such as those built
using the MFC before .NET. Central to Windows Forms is the
Control class, the foundation of all UI applications ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access