Home > Articles

0672322323

Like this article? We recommend

Programming with the Framework Class Library

Because the Framework Class Library contains classes in the true object-oriented spirit of that word, there are two primary ways that you will find yourself using these base classes: as black boxes that you can call into, and as classes that you can inherit from and extend to craft your own functionality.

Instantiating Objects from the Class Library

The use of base classes as a black box is probably the primary path for most developers; in this mode, your code will be treating the class library as a simple API to get at core, base functions on your particular operating system.

Using the class library classes in this manner does not represent a departure from the programming model that Visual Basic developers are used to. As an example, if you have programmed Visual Basic applications that have made use of the ADO library, you probably did the following:

  1. You set a reference to the code library through the VB IDE

  2. You Dim'd a container for one of the ADO objects

  3. After you had a container object, you instantiated a version of an ADO object into it

  4. After that, you simply invoked its methods and properties as needed.

With Visual Basic.NET, your consumption of Framework classes will follow the exact same pattern.

NOTE

Not all classes in the Framework Class Library allow you to create instances just by using the New operator—some force you to go through a class factory method to get your initial instance of the class. The WebRequest class is one example: in order to create a new WebRequest object, you have to use the WebRequest.Create method. You should also be aware that some classes have static methods and properties. Static methods apply to classes and not instances. That means that you don't have to create an instance of the class in order to use the method. The WebRequest.Create method is an example of a static method: we simply call it using the class reference without an actual instance having been created.

Inheriting from the Framework Class Library

With the exception of those classes marked as sealed, you are free to build your own classes on any of the base classes in the library using the inheritance model in .NET.

As you explore the Framework Class Library, you will see many instances of inherited classes that override and overload class members (both of these concepts were discussed in the previous chapter. In the documentation for a specific class, you may see a method defined as Overrides:

Overrides Public Function GetYear(ByVal time As DateTime) As Integer

This example shows the method prototype for the GetYear method on the JulianCalendarClass. It shows us that this function is overridden from its base class (in this case, from the Calendar class).

Overloading is a form of overriding by providing multiple method instances that different only in their parameter list.

As with overriding, you will notice plenty of examples of overloading. Many class constructors are overloaded to give developers the maximum choice of instantiation based on the available data.

Consider the following constructors for the TCPClient class:

Overloads Public Sub New()

Overloads Public Sub New(ByVal localEP As IPEndPoint)

Overloads Public Sub New(ByVal hostname As String, port As Integer)

These constructors give you the choice of how you want to instantiate a TCPClient object.

NOTE

By now you'll have noticed that both Visual Basic.NET and the Framework Class Library define base data types. In other words, you have the Int32 data type defined in the System root namespace, and the Integer data type defined in Visual Basic. From a best practices perspective, you may be asking yourself, which is the preferred method: declaring things using VB.NET intrinsics, or their actual System types?

To illustrate, both of the following lines of code are valid:

Dim SomeVar As Integer

Dim AnotherVar As System.Int32

We suggest you pick whatever comes more naturally to you, and use it consistently. Using the actual framework data types has some attraction if you are programming across multiple languages; you don't have to shift gears. On the other hand, dimensioning a variable as Integer will come much more naturally to Visual Basic developers. And of course, you don't have to worry about the repercussions of your choice: the CLR ensures that all of your code is mapped to the correct underlying data type.

Exception Handling

Exception Handling is the process of managing errors that may be encountered during the execution of your code. The .NET runtime and the .NET languages support the concept of Structured Exception Handling (SEH). These exception handlers follow a standard format that defines a Try block, a Catch block, and a Finally block.

Writing an exception handler requires you to place the code that could possibly generate an error into the Try block. In the Catch block, you place your code that deals with the error. The Finally block is where you place operations that should be performed regardless of whether an error was raised or not. The following code snippet shows a simple routine that implements its code inside of an exception handler.

  Sub DoCalc(ByVal num1 As Integer, ByVal num2 As Integer) As Integer

    'The exception handler is initiated with the 'try' block

    Try

       DoCalc = num1 / num2

    Catch appError As Exception

      'handle the error; here, we just alert the user

      'through a message box. To get more detailed 

      'debugging level info, we could use the 

      'Exception.StackTrace property...

      MsgBox("Error:" & appError.Message)



    Finally



      Beep()



    End Try

  End Sub

Notice that the Catch statement syntax allows you to deal with the exception as an object. The class library defines an actual Exception class that allows the runtime to treat pass exceptions through as instances of the Exception class. The Exception base class is, in turn, used to derive more specialized exception classes such as the ApplicationException and SystemException classes (both defined in the System root namespace) and the WebException class (defined in the System.Net namespace). In fact, a fairly deep class hierarchy is built from the Exception class base (see Figure 4.1).

As you examine the Exception class descendants, you will see that they offer methods and properties specific to a given coding scenario. They often, for instance, override the ErrorCode property to provide specific error codes for their particular scope. An exception handler with multiple catch blocks looks like this:

    'The exception handler is initiated with the 'try' block

    Try

       'code that could raise an exception goes here

    Catch appError As Exception

      'handle the generic error



    Catch win32Error As Win32Exception

      'handle win32 error



    Catch sockError As SocketException

      'handle network socket error



    Finally



      'code to run regardless of exception or not



    End Try

You can use the appropriate level (generalized or specialized) of exception object that is appropriate to your specific piece of code. You often will use multiple catch blocks in your code to deal with exceptions raised across different levels of the exception class hierarchy.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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