Home > Articles > Programming > Windows Programming

  • Print
  • + Share This
This chapter is from the book

The Elements of a Namespace

Each namespace can define its own set of classes, structures, delegates, interfaces, and enumerations. And, as we have seen with the System namespace, they can also sometimes contain value types. Let's examine each one of these in turn.


As we discussed in Chapter 3, a class is a template or blueprint for an object. It defines how an object should look and behave. It does this principally through methods, properties, and events.

If you have read on from the last chapter or have some experience with object-oriented programming, you should be familiar by now with the concepts of classes. You should note, however, that the .NET runtime supports some class attributes that you may not be familiar with. These attributes are summarized in Table 4.2.

TABLE 4.2 .NET Class Attributes

Class Attribute



Specifies that you cannot inherit from this class. A good example of a sealed class in the Framework Class Library is the String class. In Visual Basic .NET you can create your own sealed classes by using the NotInheritable keyword.


Specifies the interfaces implemented by a particular class. For instance, the Array Class implements the Ilist interface, imbuing Arrays with the capability to add members and retrieve the index of a member.


Indicates that the class cannot be directly instantiated. They typically exist as a means of organizing lower-level derived classes, or as a convenient virtual class that is used solely as a template for other classes instead of instances. Examples of abstract classes include the XMLWriter class in the System.XML name-space, and the Image class in the System.Drawing namespace.


Identifies the base class that the current class inherits from. As an example, the ColorDialog Class inherits from the CommonDialog class—an acknowledgment of the fact that it is a type of common dialog.

Exported/Not Exported

Indicates whether a class is visible outside of its defining assembly. Exported classes are those visible outside of the assembly in which they are defined.

Classes typically define a constructor; this is a specialized behavior of a class that is called whenever a new instance is created from that class. In Visual Basic .NET, you will define your constructors using the Sub New routine. Class_Initialize and Class_Terminate events are no longer supported. Classes may also implement destructors that will be called when the object is being destroyed.

Object destruction in .NET works a little bit differently than you have come to expect. .NET implements something called a garbage collector. The garbage collector continually examines a "reference tree;" if it finds an object that doesn't have any more branches on the reference tree, it calls the destructor of that object. It is no longer necessary to explicitly destroy managed objects; the garbage collector will take care of it for you.


If your class uses resources that are unmanaged in nature, you should implement a Finalize method. This method, which is not public, will be called by the garbage collector as it destroys unneeded objects. If you need to provide a public method for freeing resources (such as a Close method for your class), you should implement the IDisposable interface.

All objects in the .NET Framework inherit from the System.Object class. System.Object is the ultimate superclass in the Framework Class Library.


Structures are the .NET version of user-defined types from prior versions of Visual Basic. User Defined Type (or UDT) syntax in Visual Basic, versions 6 and earlier, looked something like this:

Type InventoryItem 
   SKU As String * 50 
   Price As Single 
   Name As String * 25 
   Count As Integer 
End Type 

The metamorphosis into structures means the Type...End Type syntax is no longer supported. It has been replaced with Structure...End Structure:

Structure InventoryItem 
   Public SKU As String 
   Private Price As Single 
   Public Name As String 
   Private Count As Integer 
End Structure 

Note that with structures, each structure element can have its own scope modifier (for example, can be public, private, and so on). This was not previously possible with UDTs.

And that's not all that has changed. Structures in .NET behave a lot like classes. They support most of the constructs of a class including properties, methods, and events. Table 4.3 summarizes some of the key similarities and differences between classes and structures.

TABLE 4.3 Structures versus Classes




Allows parameter-less constructors?



Supports properties, methods, and events?



Can be inherited from?



Can implement interfaces?



Support for destructors?



In the class library, structures are used to represent value types such as integers (Int16, Int32, Int64). In fact, the actual structure object inherits directly from the class ValueType in the root System namespace.


Delegates may be an unfamiliar concept to the average Visual Basic developer. In essence, delegates are function pointers: They encapsulate method calls to other objects. Delegates are described by the parameters they accept and the value type they return. In other words, you can declare a delegate that will map to a method call that takes an integer and a single and returns a string:

public delegate myDelegate(value1 As Integer, value2 As Single) As String 

To use the delegate, you would declare a variable that references the delegate like this:

Dim myCallback As myDelegate = New myDelegate(obj.SomeMethod) 

If the SomeMethod method that you reference has a function signature that matches the definition of myDelegate, you are home free, otherwise an error will be raised.

One of the powerful capabilities of a delegate is its ability to perform its function pointing in a late bound fashion. You can use the preceding delegate to map to any method that follows the parameter and return type signature; you don't need to explicitly make a tie between the delegate and a specific function at design time.

Delegates are defined throughout the Framework Class Library namespaces and fulfill a variety of different tasks, most associated with implementing designs regarding callbacks and event processing.


An interface is most commonly described as a contract. If you implement an interface, you are essentially entering into a contract with all other components that exist that says, "I agree to provide the following functionality in the following manner forever and ever...." Interfaces can have methods and properties just like classes.

You can implement interfaces defined in the Framework Class Library by using the Implements keyword:

Public Class Class1 
   Implements IDisposable 
   Public Sub Finalize() Implements IDisposable.Dispose 
   End Sub 
End Class 

This code snippet shows a class implementing the IDisposable interface.

Back when we talked about inheritance and code reuse in Chapter 3, we said that interfaces provide a good structure for implementing code belonging to a class that isn't necessarily "logically" related to our core class.

This kind of code reuse keeps our class hierarchies from becoming cluttered with seemingly random inheritance relationships.


There are some design considerations to think about when deciding between class inheritance and interface implementation. For instance, because interfaces are meant to be binding and perpetual contracts, they can't (or shouldn't) be changed. Implementing code in an interface that is likely to change, such as business rules, leads to a very brittle architecture. You don't have this concern with class inheritance because methods and properties can always be added to a base class without "breaking" its descendant classes.


An enumeration is essentially a named constant—it is an aid to developer productivity because it allows you to reference values using a recognizable name. Using enumerations greatly improves code readability and speeds up coding because they provide a way to name or reference a value that maps to one of the underlying data types defined by the CTS. Visual Basic developers should be familiar with the concept of "enums"—the syntax has not changed moving into Visual Basic .NET. The .NET runtime allows enumerations to evaluate to any of the signed or unsigned integer data types that are defined (such as Int32, Int64, and so on).

As far as the Framework class library is concerned, enumerations are in many of the name-spaces. One example of an enumeration in the class library is Appearance, contained in the System.Windows.Forms namespace.

To use an enumeration from your code, simply reference the enumeration's name and the value name that you want to use:


In the preceding code, we use the Appearance enumeration to specify that the button control we are using should take on the "Button" appearance.

Enumerations are derived from the System.Enum class, which means you can reference enumerations in some very cool ways. For instance, you can call the GetValues() method to get an array of all values defined by an enumeration. You can also call the GetNames() method to get an array of all names for the values defined by an enumeration.

  • + Share This
  • 🔖 Save To Your Account

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