Message-ID: <466829932.1489.1386938703972.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1488_1823478667.1386938703972" ------=_Part_1488_1823478667.1386938703972 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Namespaces are useful because if you have, for example, a <=
namespace and a
amespace, and they both have a
you can refer to
Furniture.Leg and be=
clear about which
class you are mentioning.
To declare a
namespace, all that is required is that you pu=
namespace followed by a name at the top of your file.
This creates your
Tutorial.Thing. While =
coding inside your
namespace, it will be transparently
To declare a
namespace within a
t place a dot . inbetween each other.
classes from another
namespace, you wou=
ld use the
The most common
ce you will import is
Both produce the exact same code, it's just easier and clearer with the =
If you are importing from another assembly, you would use the phrase
System.Data is part of an external library which can be add=
ed, System.Data.dll. Gtk is part of the Gtk# library, which, since it has a=
special name (with a dash in it), it must be quoted.
Go on to Part 13= - Enumerations