CS0118: 'Mediator' is a namespace but is used like a type

[Houzhendong]

for better performance, i chose Mediator instead of IMediator, but i get CS0118: 'Mediator' is a namespace but is used like a type error, so i have to explicitly declare Mediator by "MyNameSpace.Mediator" for every call , do you have better way to solve this ?

example

using Microsoft.Extensions.DependencyInjection;

namespace ConsoleApp1
{
    internal class Program
    {
        private static void Main(string[] args)
        {
            var service = new ServiceCollection()
                .AddMediator(options => options.Namespace = "MyNamespace")
                .BuildServiceProvider();
        }
    }

    public class Test
    {
        private readonly IServiceProvider _service;

        public Test(IServiceProvider service)
        {
            _service = service;
        }

        public void ResolveMediator()
        {
            Mediator mediator = _service.GetRequiredService<Mediator>(); // here i will get cs0018 error
            MyNamespace.Mediator mediator1 = _service.GetRequiredService<MyNamespace.Mediator>(); // this will work, but i wanna know is there any better way to avoid type "MyNamespace." every time 
        }
    }
}

[gabrielacos]

Can add an "s" at the end of your namespace. It may be confusing it with Mediator packages.

[martinothamar]

Ahh, no matter what namespace is configured, the Mediator implementation will always collide with the Mediator namespace from the abstractions package (where IRequest etc is). One option is to create a global alias using global usings: global using MyMediator = MyNamespace.Mediator or similar. I'll have to think about refactoring this without having too many breaking changes... Thanks for bringit it up 👍

[Meryovi]

I have stumbled upon this one. You can also use Mediator.Mediator instead of just Mediator and it will work properly.

[TimothyMakkison]

I keep getting a MSBuildLocator error. In the past I've fixed similar issues by installing NuGet.Frameworks.