Possible Conflict with Class name & Property Name?

Question

If you have a namespace that contains a property in ClassA and a class that has the name of that Property somewhere else in your project and both are in the same namespace this won't cause conflicts will it?

So lets say I have a class named Car

namespace Dealer
{
   class Vehicle
   {
        // the main class that defines vehicle, so this is Dealer.Vehicle  (Vehicle.cs)
   }
}

and a property over in some other class

namespace Dealer
{
    class Dealer
    {
        public Vehicle Vehicle
        {
           get { return _vehicle; }
        }
    }
}

so for the second it is really this for the property

public Dealer.Vehicle Vehicle
{
     get { return _car; }
}

so now you have Dealer.Vehicle and Dealer.Dealer.Vehicle. Wondering of that would cause a conflict ever.

If both those classes are in the same namespace and

Answer 1

namespace Dealer
{
    class Dealer
    {
        ...
    }
}

Wondering if that would cause a conflict ever.

Yes, that will cause problems. Do not name a class the same as its namespace. Eric Lippert has written a series of articles about this.

• Part One: Collisions amongst referenced assemblies
• Part Two: Machine-generated code
• Part Three: Bad hierarchical design
• Part Four: Making the problem worse

Answer 2

First off, do not name the class the same as its namespace.

Second, having a property of the same name as its class will work fine, as I have done it often.