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

// Note we are not "using" MyShapes anymore.

using System;

namespace MyApp

{

class ShapeTester

{

static void Main(string[] args)

{

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

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

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

}

}

}

Typically there is no need to use a fully qualified name. Not only does it require a greater num-

ber of keystrokes, but also it makes no difference whatsoever in terms of code size or execution

speed. In fact, in CIL code, types are 

always defined with the fully qualified name. In this light, the

C# using keyword is simply a typing time-saver.

However, fully qualified names can be very helpful (and sometimes necessary) to avoid name

clashes that may occur when using multiple namespaces that contain identically named types.

Assume you have a new namespace termed My3DShapes, which defines three classes capable of ren-

dering a shape in stunning 3D: