ComponentOne Scheduler for ASP.NET: ComponentOne Scheduler for ASP.NET AJAX Overview > Namespaces

Namespaces

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 Web products is C1.Web.UI.Controls. The following code fragment shows how to declare a C1Schedule using the fully qualified name for this class:

      Visual Basic

Dim Schedule As C1.Web.UI.Controls.C1Schedule

      C#

C1.Web.UI.Controls.C1Schedule Schedule;

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.

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:

      Visual Basic

Imports C1Schedule = C1.Web.UI.Controls.C1Schedule

Imports MySchedule = MyProject.Objects.C1Schedule

 

Dim shedule1 As C1Schedule

Dim schedule2 As MySchedule

      C#

using C1Schedule = C1.Web.UI.Controls.C1Schedule;

using MySchedule = MyProject.Objects.C1Schedule;

 

 C1Schedule schedule1;

 MySchedule schedule2;

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.


Send comments about this topic to ComponentOne.
Copyright ComponentOne LLC. All rights reserved.