'namespace' but is used like a 'type'

C#ClassNamespaces

C# Problem Overview


My program uses a class called Time2. I have the reference added to TimeTest but I keep getting the error, 'Time2' is a 'namespace' but is used like a 'type'.

Could someone please tell me what this error is and how to fix it?

namespace TimeTest
{
  class TimeTest
  {
    static void Main(string[] args)
    {
        Time2 t1 = new Time2();
    }
  }
}

C# Solutions


Solution 1 - C#

I suspect you've got the same problem at least twice.

Here:

namespace TimeTest
{
    class TimeTest
    {
}

... you're declaring a type with the same name as the namespace it's in. Don't do that.

Now you apparently have the same problem with Time2. I suspect if you add:

using Time2;

to your list of using directives, your code will compile. But please, please, please fix the bigger problem: the problematic choice of names. (Follow the link above to find out more details of why it's a bad idea.)

(Additionally, unless you're really interested in writing time-based types, I'd advise you not to do so... and I say that as someone who does do exactly that. Use the built-in capabilities, or a third party library such as, um, mine. Working with dates and times correctly is surprisingly hairy. :)

Solution 2 - C#

namespace TestApplication // Remove .Controller
{
    public class HomeController : Controller
    {
       public ActionResult Index()
        {
            return View();
        }
    }
}

Remove the controller word from namepsace

Solution 3 - C#

All the answers indicate the cause, but sometimes the bigger problem is identifying all the places that define an improper namespace. With tools like Resharper that automatically adjust the namespace using the folder structure, it is rather easy to encounter this issue.

You can get all the lines that create the issue by searching in project / solution using the following regex:

namespace .+\.TheNameUsedAsBothNamespaceAndType

Solution 4 - C#

If you're working on a big app and can't change any names, you can type a . to select the type you want from the namespace:

namespace Company.Core.Context{
  public partial class Context : Database Context {
    ...
  }
}
...

using Company.Core.Context;
someFunction(){
 var c = new Context.Context();
}

Solution 5 - C#

I had this problem as I created a class "Response.cs" inside a folder named "Response". So VS was catching the new Response () as Folder/namespace.

So I changed the class name to StatusResponse.cs and called new StatusResponse().This solved the issue.

Solution 6 - C#

The class TimeTest is conflicting with namespace TimeTest.

If you can't change the namespace and the class name:

Create an alias for the class type.

using TimeTest_t = TimeTest.TimeTest;

TimeTest_t s = new TimeTest_t();

Solution 7 - C#

Please check that your class and namespace name is the same...

It happens when the namespace and class name are the same. do one thing write the full name of the namespace when you want to use the namespace.

using Student.Models.Db;

namespace Student.Controllers
{
    public class HomeController : Controller
    {
        // GET: Home
        public ActionResult Index()
        {
            List<Student> student = null;
            return View();
        }
    }

Solution 8 - C#

If you are here for EF Core related issues, here's the tip:

Name your Migration's subfolder differently than the Database Context's name.

This will solve it for you.

My error was something like this: ModelSnapshot.cs error CS0118: Context is a namespace but is used like a type

Solution 9 - C#

if the error is

Line 26:
Line 27: @foreach (Customers customer in Model) Line 28: { Line 29:

give the full name space
like @foreach (Start.Models.customer customer in Model)

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTheAceView Question on Stackoverflow
Solution 1 - C#Jon SkeetView Answer on Stackoverflow
Solution 2 - C#shobaView Answer on Stackoverflow
Solution 3 - C#Alexei - check CodidactView Answer on Stackoverflow
Solution 4 - C#James L.View Answer on Stackoverflow
Solution 5 - C#AniView Answer on Stackoverflow
Solution 6 - C#Mats GausdalView Answer on Stackoverflow
Solution 7 - C#Muhammad Usama ArshadView Answer on Stackoverflow
Solution 8 - C#Andrei IovanView Answer on Stackoverflow
Solution 9 - C#Nelcon CroosView Answer on Stackoverflow