This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// Another shapes namespace...

using System;

namespace My3DShapes

{

// 3D Circle class

class Circle{ }

// 3D Hexagon class

class Hexagon{ }

// 3D Square class

class Square{ }

}

If you update ShapeTester as was done here, you are issued a number of compile-time errors,

because both namespaces define identically named types:

// Ambiguities abound!

using System;

using MyShapes;

using My3DShapes;

namespace MyApp

{

class ShapeTester

{

static void Main(string[] args)

{

// Which namespace do I reference?

Hexagon h = new Hexagon(); // Compiler error!

Circle c = new Circle();   // Compiler error!

Square s = new Square();   // Compiler error!

}

}

}

C H A P T E R   1 5  

■

I N T R O D U C I N G   . N E T  A S S E M B L I E S

477

8849CH15.qxd  10/22/07  1:46 PM  Page 477

---

The ambiguity can be resolved using the type’s fully qualified name:

// We have now resolved the ambiguity.

static void Main(string[] args)

{

My3DShapes.Hexagon h = new My3DShapes.Hexagon();

My3DShapes.Circle c = new My3DShapes.Circle();

MyShapes.Square s = new MyShapes.Square();

}