Home > Articles > Programming > Windows Programming

Overview of .NET Framework Classes

Overwhelmed by the numerous classes found in .NET? Acquaint yourself with the most commonly used classes by looking at key concepts and patterns found throughout the .NET framework.
This chapter is from the book

It is impossible to cover in one chapter, or even in one book, all of the .NET Framework classes. Although coverage is incomplete, the .NET classes cover a large fraction of the Win32 API, as well as much else. While a lot of attention has been focused on the Internet-related functionality, the development model for Windows applications has changed as well.

This chapter focuses on those classes that illustrate the key concepts and patterns that appear throughout the .NET Framework. You will find this approach more fruitful over the long run than our attempting to explain a little about every class that you might need without giving you much insight. Other chapters will go into more depth about other parts of the framework, such as Windows Forms, ASP.NET, ADO.NET security, and Web Services.

We start out by exploring the concept of reflection and metadata. Metadata appears everywhere in .NET and is critical to understanding how the Common Language Runtime (CLR) can provide services for your applications. Next, we explore file input/output for several reasons. First, it introduces the important topic of serialization. Second, the Path class provides an example of how some framework classes provide some or all of their functionality through static methods. Third, the formatter classes are used in several places in .NET.

Understanding serialization will give you a concrete idea of how the framework can handle objects transparently for you. It also appears in a supporting role any place where objects have to be stored or transported. Our discussion of the ISerializable interface again demonstrates how much easier it is to implement an interface in .NET than with COM.

To further develop an understanding of the .NET model for applications, we introduce programming with threads under .NET and several .NET synchronization techniques to handle multithreading conflicts. The various synchronization techniques illustrate the tradeoffs of using attributes supplied by the framework versus doing it your self.

To further your understanding of the .NET programming model, we introduce context and the use of proxies and stubs to implement system services. We also look at using application domains, which are more efficient than Win32 processes in achieving application isolation.

The asynchronous design pattern appears throughout .NET and is discussed in some detail. We give some examples of remoting because it is a key technology and it summarizes many of the concepts developed in this chapter. The chapter uses several attributes provided by the .NET Framework, and we show how to implement and use custom attributes. We discuss finalization so that you can understand how to make sure resources are properly freed in your applications.

Metadata and Reflection

The Serialization example in Chapter 2 demonstrates how metadata makes many of the services of the CLR possible. Many of the technologies we cover in the rest of the book rely on metadata, although we will not always stop and point this out.

Metadata is information about the assemblies, modules, and types that constitute .NET programs. If you have ever had to create IDL to generate a type library so that your C++ COM objects could be called by Visual Basic, or to create proxies and stubs, you will appreciate how useful metadata is and will be grateful that it comes "for free."

Compilers emit metadata, and the CLR, the .NET Framework, or your own programs can use it. Since we want to give you an understanding of how metadata works, we will focus our discussion on the use of metadata, not the creation of metadata. Metadata is read using classes in the System::Reflection namespace.1

When you load an assembly and its associated modules and types, the metadata is loaded along with it. You can then query the assembly to get those associated types. You can also call GetType on any CLR type and get its metadata. GetType is a method on System::Object, which every CLR type inherits from. After you get the Type associated with an object, you can use the reflection methods to get the related metadata.

The Reflection sample program takes the case study's Customer assembly and prints out some of the metadata available. You should examine the output and source code as you read the next sections. You should especially compare the output of the program with the source code in the file customer.h.

The program clearly shows that it is possible to retrieve all of the types in an assembly and reconstruct the structures, interfaces, properties, events, and methods associated with those types.

First we load the assembly into memory and write out its name.

Assembly *a = Assembly::Load(assemblyName);
   "Assembly {0} found.", a->FullName);

The output for this statement is appropriate for an unsigned assembly:

Assembly Customer, Version=1.0.643.18973, Culture=neutral, @@PublicKeyToken=null found.

One of the properties of the Assembly class is the CodeBase, discussed Chapter 7, "Assemblies and Deployment." The security evidence associated with this assembly is another property.

The following code tries to get the entry point for the assembly:

MethodInfo *entryMethodInfo = a->EntryPoint;

Since this is a typical C++ component assembly, the entry point is __DllMainCRTStartup@12. If this was an executable program, we could use the Invoke method on the MethodInfo class to run the startup code in the assembly.2

The sample uses the assembly's GetModules method to find associated modules with this assembly. In this case we have only one, named customer.dll. We could then find the types associated with the module. Instead, we use the assembly's GetTypes method to return an array of the assembly's types.


The abstract class Type in the System namespace defines .NET types. Since there are no functions outside of classes or global variables in .NET, getting all the types in an assembly will allow us to get all the metadata about the code in that assembly. Type represents all the types present in .NET: classes, structs, interfaces, values, arrays, and enumerations.

The Type class is also returned by the GetType method on the System::Object class and the static GetType method on the Type class itself. The latter method can be used only with types that can be resolved statically.

One of Type's properties is the assembly to which it belongs. You can get all the types in the containing assembly once you have the Type of one object. Type is an abstract class, and at runtime an instance of System::RuntimeType is returned.

If you examine the program's output, you will see that each type in the assembly, CustomerListItem, ICustomer, Customer, and Customers, is found and its metadata is printed out. We can find out the standard attributes and the type from which the class derives for each type through the Attributes and BaseType properties.

The methods associated with the Type class enable you to get the associated fields, properties, interfaces, events, and methods. For example, the Customer type has no interfaces, properties, or events, but it has four fields, three constructors, and the methods inherited from its BaseType System::Object:

       public .ctor(System.String first, System.String last,
       @@System.String email)
       public .ctor()
       public .ctor(System.Int32 id)
       public Int32 GetHashCode()
       public Boolean Equals(System.Object obj)
       public String ToString()
       public Type GetType()

The type Customers inherits from one interface and has one constructor and four of its own methods in addition to the four it inherited from its BaseType System::Object:

      public .ctor()
      public Void ChangeEmailAddress(System.Int32 id,
      @@System.String emailAddress)
      public ArrayList GetCustomer(System.Int32 id)
      public Void UnregisterCustomer(System.Int32 id)
      public Int32 RegisterCustomer(System.String firstName,
@@      System.String lastName, System.String emailAddress)
      public Int32 GetHashCode()
      public Boolean Equals(System.Object obj)
      public String ToString()
      public Type GetType()

These were obtained with the GetInterfaces, GetFields, GetProperties, GetEvents, GetConstructors, and GetMethods methods on the Type class. Since an interface is a type, GetInterfaces returns an array of Types representing the interfaces inherited or implemented by the Type queried. Since fields, properties, events, and methods are not types, their accessor methods do not return Types. Each of their accessor methods returns an appropriate class: FieldInfo, PropertyInfo, EventInfo, ConstructorInfo, and MethodInfo. All these classes, as well as the Type class, inherit from the MemberInfo class that is the abstract base class for member metadata.

Let us examine some of the metadata associated with a class method. Using the reflection methods, we were able to reconstruct the signatures for all the classes and interfaces in the Customer assembly. Here is the output for the methods of the Customers class:

   public Void ChangeEmailAddress(System.Int32 id,
@@   System.String emailAddress)
   public ArrayList GetCustomer(System.Int32 id)
   public Void UnregisterCustomer(System.Int32 id)
   public Int32 RegisterCustomer(System.String firstName,
@@   System.String lastName, System.String emailAddress)
   public Int32 GetHashCode()
   public Boolean Equals(System.Object obj)
   public String ToString()
   public Type GetType()

Here is the code from the example that produced the output:

   for (int j = 0; j < methodInfo.Length; j++)
      if (methodInfo[j]->IsStatic)
         Console::Write("        static ");
      if (methodInfo[j]->IsPublic)
         Console::Write("        public ");
      if (methodInfo[j]->IsFamily)
         Console::Write("        protected ");
      if (methodInfo[j]->IsAssembly)
         Console::Write("        internal ");
      if (methodInfo[j]->IsPrivate)
         Console::Write("        private ");
         "{0} ", methodInfo[j]->ReturnType->Name);
         "{0}(", methodInfo[j]->Name);
      ParameterInfo *paramInfo [] =
      long last = paramInfo->Length - 1;
      for (int k = 0; k<paramInfo->Length; k++)
            "{0} {1}",
         if (k != last)
            Console::Write(", ");

Except that a constructor does not have a return type, the exact same code reconstitutes the calling sequences for the class's constructors.

The MethodInfo class has properties that help us determine if the method is static, public, protected, internal, or private as well as determine the return type and method name. The method parameters are stored in a property array of type ParameterInfo class.

This example should also make it clear that types are assembly relative. The same type name and layout in two different assemblies are treated by the runtime as two separate types. When versioning assemblies, you have to be careful when mixing versioned types or the same types in two different assemblies.

All this metadata allows the CLR and the framework to provide services to your applications, because they can understand the structure of your types.

Late Binding

Reflection can also be used to implement late binding. Late binding is where the method to be called is determined during execution rather than at compilation time. It is one example of how metadata can be used to provide functionality. As the previous example demonstrates, you can extract the signature of a method associated with a type. The MethodInfo object has all the needed metadata for a class method. The Dynamic sample demonstrates a very simple example of late binding.3

We dynamically load an assembly and get the metadata for a method of a particular type:

   // Load Customer assembly
   Assembly *a = Assembly::Load("Customer");

   // Get metadata for Customers class and one method
   Type *t = a->GetType("OI.NetCpp.Acme.Customers");
   MethodInfo *mi = t->GetMethod("GetCustomer");

One thing that C++ programmers need to remember when doing reflection programming is that when you deal with strings that contain namespaces or classes, you must use properly formatted strings that are understood by the reflection class methods. So, the fully qualified class name in the code above is OI.NetCpp.Acme.Customers rather than the C++ style format OI::NetCpp::Acme::Customers. Thus, the format used is like that of C#, not C++.

Using the reflection classes, we could have made this completely dynamic by arbitrarily picking types, methods, and constructors from the Customer assembly using the techniques of the last example, but we wanted to keep the Dynamic example simple. A more ambitious program could do something much more interesting, such as implement an assembly decompiler that generates Managed C++, C#, or VB.NET source code directly from a compiled assembly.

The System namespace has an Activator class that has overloaded CreateInstance methods to create an instance of any .NET type using the appropriate constructor. The Activator class is discussed in this chapter's section on remoting. We invoke a constructor with no arguments to create an instance of the Customers object.

   Type *t = a->GetType("OI.NetCpp.Acme.Customers");
   Object *customerInstance =

We then build an argument list and use the Invoke method of the MethodInfo instance to call the GetCustomer method.

   // invoke the method
   Object *arguments [] = new Object*[1];
   int customerId = -1;
   arguments[0] = __box(customerId);
   Object *returnType = mi->Invoke(
      customerInstance, arguments);

Using the reflection methods, we get the type information for each field in a return structure. Note that the GetValue method of FieldInfo returns the data for a particular field in an object.

   if (returnType->GetType() ==
      ArrayList *arrayList =
         dynamic_cast<ArrayList *>(returnType);
      for (int i = 0; i<arrayList->Count; i++)
         Type *itemType =
         FieldInfo *fi [] = itemType->GetFields();
         for (int j = 0; j < fi->Length; j++)
            Object *fieldValue =
               "{0, -10} = {1, -15}",
               fi[j]->Name, fieldValue);

Again, note the use of the single periods rather than double colons in the string System.Collections.ArrayList.

This code did not use any specific objects or types from the Customer assembly. We did use some knowledge about the assembly to keep the code simple to illustrate the main points. It should be clear, however, how to make this completely general.

You can take this one step further and use the classes that emit metadata (in System::Reflection::Emit). You can even dynamically create an assembly in memory, and then load and run it!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020