Namespaces organize the objects defined in an assembly. Assemblies can contain multiple namespaces, which can in turn contain other namespaces. Namespaces prevent ambiguity and simplify references when using large groups of objects such as class libraries.
The general namespace for ComponentOne Windows products is C1.Win. The namespace for the PrintPreview control is C1.Win.C1PrintPreview. The following code fragment shows how to declare a C1PrintPreview control using the fully qualified name for this class:
Dim preview As C1.Win.C1PrintPreview.C1PrintPreview
• C#
C1.Win.C1PrintPreview.C1PrintPreview preview;
Namespaces address a problem sometimes known as namespace pollution, in which the developer of a class library is hampered by the use of similar names in another library. These conflicts with existing components are sometimes called name collisions.
For example, if you create a new class named Pages, you can use it inside your project without qualification. However, the C1PrintPreview assembly also implements a class called Pages. So, if you want to use the C1PrintPreview class in the same project, you must use a fully qualified reference to make the reference unique. If the reference is not unique, Visual Studio .NET produces an error stating that the name is ambiguous. The following code snippet demonstrates how to declare these objects:
' Define a new object based on your Pages class.
Dim MyPages as Pages
' Define a new C1PrintPreview.Pages object.
Dim PreviewPages as C1.Win.C1PrintPreview.Pages
• C#
// Define a new object based on your Pages class.
MyPages as Pages;
// Define a new C1PrintPreview.Pages object.
PreviewPages as C1.Win.C1PrintPreview.Pages;
Fully qualified names are object references that are prefixed with the name of the namespace where the object is defined. You can use objects defined in other projects if you create a reference to the class (by choosing Add Reference from the Project menu) and then use the fully qualified name for the object in your code.
Fully qualified names prevent naming conflicts because the compiler can always determine which object is being used. However, the names themselves can get long and cumbersome. To get around this, you can use the Imports statement (using in C#) to define an alias — an abbreviated name you can use in place of a fully qualified name. For example, the following code snippet creates aliases for two fully qualified names, and uses these aliases to define two objects:
Imports C1Pages = C1.Win.C1PrintPreview.Pages
Imports MyPages = MyProject.Objects.Pages
Dim p1 As C1Pages
Dim p2 As MyPages
• C#
using C1Pages = C1.Win.C1PrintPreview.Pages;
using MyPages = MyProject.Objects.Pages;
C1Pages p1;
MyPages p2;
If you use the Imports statement without an alias, you can use all the names in that namespace without qualification provided they are unique to the project.
|
