Ambiguous references with the same namespace

Question

The RC class is not connected to the database; it is a simple class. The class is located in only one place and is not partial. The Aérochem.Domain dll project compiles just fine.

Note. If I select one of two identical namespaces in the quick fix menu, it does nothing.

Note2: This happens with several classes (some are database related and some are not)

Is there a fix for this or a way to figure out what's wrong?

Answer 1

I had the same problem. I am using ReSharper. The solution to my problem is not to clear the solution, but to delete the suo file. Hope this helps.

Answer 2

As for the link for future users: this topic covers four answers, while two in the comments. I ran into a problem several times, three of these answers have helped me in the past, so if you run into the same problem, try any of them:

• Clean and / or reinstall the solution, then reanalyze the files in Resharper.
• Restart Visual Studio, then re-analyze
• Delete the bin folder / then re-analyze
• (Obviously, deleting the suo file may also help, although I never had to do this, and I can't figure out how this should help)
• The combination of the three above.

(This is not a completely new answer, it is rather a comment on the many answers and comments found - this is a community wiki, so do not hesitate to adapt it if necessary)

Answer 3

For ReSharper users who, like me, do not want to remove their *.suo file solution:

Clear your caches via: ReSharper → Options → Environment → General → Clear Caches !

Thanks for the comment on this comment AUSTX_RJL . I wanted his valuable information to become more visible.

Answer 4

.dll already in my /bin .

When I deleted it, he got rid of this error.

Answer 5

I had this problem as well as ReSharper installed on visual studio.

I open the big code on the ReSharper tracker , and the development team advised me to do:

Decision:

This problem can be resolved by removing Solution User Options (.Suo) File . This file is stored in the root of the project, but is hidden. you need to check Folder Options-> View-> Show hidden files, folders, drives. , and you need to close the visual studio if you opened this project because it is used by the visual studio.

Answer 6

If your project structure contains more than one project under one solution, you must delete the contents of the bin folder in each project. This resolved the error I encountered.

Answer 7

In my case, I referenced proyect X internally. So the problem is not ReSharper (but it was ReSharper that added the link ...)

Answer 8

I had this problem in a standard .NET project (I call it a host project). The namespace causing the problem was in another project with a link (which was also a standard .NET project) in the same solution.

I did everything: clear, delete resharper caching, close soln, delete.suo, delete binary files. Nothing seemed to work.

Then I converted the host project to the .NET framework, and then the problem disappeared.

Answer 9

For me, this was because I referenced the DLL both under the Project link and the Assembly link. Fixed problem with deleting assembly link.

Answer 10

I had the same problem, while two packages ambiguously referenced the same dll, and this worked for me:

I gave alias name one of the packages (called Dapper.StrongName) by putting in my .csproj file:

  <Target Name="ChangeNameAlias" BeforeTargets="FindReferenceAssembliesForReferences;ResolveReferences"> <ItemGroup> <ReferencePath Condition="'%(FileName)' == 'Dapper.StrongName'"> <Aliases>AliasName</Aliases> </ReferencePath> </ItemGroup> </Target> 

And then added namespace using AliasName::Dapper;

I added a post here: Ambiguous Extension Methods

See related articles:

• external alias (C # Reference)
• :: operator (C # Reference)
• C # 2.0: using different versions of the same DLL in one application

Answer 11

I know this is a pretty old problem, but maybe it will help someone. If you use C # razor in Asp.Net Core 2+, if you have this problem.

1) Copy the contents of the file to notepad.

2) Delete the .cshtml file.

3) Create a .cshtml file with the same name.

4) Copy content from notepad to a new file

I don’t know if this is just a strange mistake or a consequence of updating the project from Core 1.0 to 2+, but this FULLY solved the problem for me. This was a problem for me both in Visual Studio 2017 and in 2019.