Common Type System—Defining a Namespace

CSharp-Online.NET:Articles

.NET Articles

Common Type System Type Systems Intro § Types and Objects § Type Unification § Reference, Value Types § Accessibility, Visibility § Type Members § Fields § Methods § Locals Overloading Argument Passing Style Pass-by-Value and Pass-by-Reference Output Parameters Managed Pointers Variable Argument Methods Methods, Subclassing Virtuals, Overriding New Slots Exception Handlers Constructors, Instantiation § Default Constructors Value Construction Constructor Chaining Field Initialization Type Initializers Unhandled Exceptions Properties § Indexers Mixed Mode Accessibility Events Operator Overloading Coercion Subclassing, Polymorphism Styles of Inheritance § Implementation Inheritance Interface Inheritance Abstract Classes Interfaces § Method Dispatch Multiple Inheritance Private Interface Inheritance Private Inheritance Accessibility Interface Reimplementation Abstract and Interface? Sealing Types and Methods Runtime Type Checking Namespaces: Organizing Types § Define a Namespace Namespace Resolution Special Types § Delegates § CTS Support Co- and Contravariance Anonymous Delegates Custom Attributes Enumerations § Flags-Style Limitations Helper Methods Generics § Further Reading §

This Book Reviewed!

© 2006 Wiley Publishing Inc.

Defining a Namespace

To place a type inside a namespace in C#, you simply wrap its declaration inside a namespace block:

namespace MyCompany.FooProject
{
   public class Foo { /*...*/ }
   public struct Bar { /*...*/ }
 
   namespace SubFeature
   {
      public class Baz { /*...*/ }
   }
}

Notice that we have a top-level namespace MyCompany.FooProject in which classes Foo and Bar reside. Their fully qualified names are MyCompany.FooProject.Foo and MyCompany.FooProject.Bar, respectively. We then have a nested namespace, named SubFeature. It’s not required to place it lexically within the enclosing namespace; we could have instead typed it out completely in the same or a separate file, that is, as MyCompany.FooProject.SubFeature. It contains a single type, Baz, whose fully qualified name is MyCompany.FooProject.SubFeature.Baz.