C#.NET Namespace name does not exist in namespace error - only when using is outside local namespace directive - why?

Using .NET 2.0, C#, Windows Forms development, Enterprise Library 3.1.

We have a project namespace (call it Project). We also have several sub-namespaces inside of that project, for example Project.Namespace1, Project.Namespace2, etc.

In one class, we define enums and such to be used with the Enterprise Library Logging block, like this:

namespace Project.Logging
{
  public static class Logging
  {
    public enum LogPriority
    {开发者_运维问答
      // enum values here
    }
  }
}

In another class, I use the enum values so I need to declare a using statement. Same project, so there is no assembly to reference, right?

If I declare the using inside of the local namespace, like this, it works fine:

namespace Project.SomeName
{
  using Project.Logging;

  // code referencing the Logging enum
}

However, if I put the using statement outside of the local namespace declaration, I get the "type or namespace name 'LogPriority' does not exist in the namespace 'Project.Logging'... Like this:

using Project.Logging;

namespace Project.SomeName
{
  // code referencing the Logging.LogPriority.whatever
}

Why is this? Has anyone run across this before?

I have run into similar (though not exactly the same) problems before when using a class that has the same name as its namespace.

Oddly enough it seemed to compile ok on some developers pc's but not on others. In the end we made sure that no namespace contained a class of the same name.

namespace Project.Logging
{  
  public static class Logging  // this is what caused the probems for me
  {   

  }
}

I also had a wired error. I cannot find any namespace which is coming from different assemblies, but begins with executing assembly name. Finally, I found out that I have set the target framework to .NET framework client profile.

Yes, most likely you have an unusual value set for the "Default Namespace" in your project properties. I would validate the project configuration.

We ran into this issue before and it all went down to ambiguous naming of the namespace and the class name.

When we tried to have our namespace as Services.Web.xxx and also add in a service reference as Services.Web.xxxx and ALSO add a references to an assembly that was named Services.Web.xxx you can only imagine the problems we ran into.

In the end to fix it we simply did a rename to make sure that there was only one instance of the Services prefix

Also you could do the following and create an alias to LogPriority to LogEnum:

using LogEnum= Project.Logging.Logging.LogPriority;

namespace Project.SomeName
{
    internal class MyClass
    {
        public MyClass()
        {
            LogEnum enum1 = LogEnum.None;
        }
    }
}
namespace Project.Logging
{
    public static class Logging
    {
        public enum LogPriority
        {
            None,
            Default
        }
    }
}

It definitely can make a difference if you have usings inside or outside the namespace. There is a good discussion here, and it is likely to be related to your default namespace settings.