当前页面位置: » 丰搜网 » 文档中心 » 详细内容
.net framework namespaces
.net framework namespaces
what is a namespace? if microsoft had simply provided a list of several
thousand classes, attempting to find or work with any specific class would
be next to impossible. although we're speculating, microsoft might have
ended up using class names such as systemdataoledbdataset and
systemtheadingthread. long names would be required in order to provide some
sort of groupings and perspective.
instead, microsoft chose to group the various classes into a hierarchical
set of namespaces. using a syntax that separates levels in the hierarchy
with dots, you'll find yourself referring to classes like this:
system.data.oledb.oledbdatareader
in this example, the .net framework provides a system namespace, a
system.data namespace, and a system.data.oledb namespace. each provides a
set of classes, and the oledbdatareader class is a part of the
system.data.oledb namespace.
imagine this scenario: you'd like to send a letter to a friend named tom
who lives across the country, and you address an envelope to tom (just
"tom"), slap on a stamp, and drop it into a mailbox. what's the chance that
the letter will get to your friend? next to none. if the u.s. postal
service had assigned each of us a local "namespace" consisting of
postalcode.state.city.streetaddress, then you might address your letter to
90012.ca.los angeles.123 smith street and have it reach your friend.
microsoft faced the same sort of issue when developing the .net framework.
therefore, each class belongs to a single namespace, and you'll use the
.net framework documentation to investigate the various classes and
namespaces.
you are probably asking yourself, which namespaces will i use most often?
this chapter discusses those namespaces you might utilize for typical web-
or windows-based business applications. this chapter will not (nor could
it) provide a full reference of every available namespace梩hat would take
several books itself.
the task of limiting the classes to be discussed in this chapter was
daunting梩here are well over 1,000 classes provided by the .net framework.
we decided to focus on classes that you're likely to use in applications
that take advantage of windows forms, web forms, web services, databases,
and xml. by using these rather broad areas as the basis for choosing the
namespaces, the list of classes we've included is large but not
overwhelming. once you understand some of these objects, working with other
objects is easier.
here's a list of the namespaces covered in this chapter:
system
system.data
system.data.oledb
system.data.sqlclient
system.io
system.text
system.collections
system.web.services
system.windows.forms
system.xml
although this seems like quite a lot of classes to cover, we'll only
provide a brief introduction to them in this chapter. you will find more
coverage of many of these namespaces in later chapters in the book.
tip
in order to follow along with the discussion in this chapter, you can load
the jumpstart\frameworkclasses\frameworkclasses.sln solution into visual
studio .net.
