Ambigous references

I have the following problem with resharper.

I have one big solution to which I add from time to time other projects for debugging. I do not change the reference to project reference but instead i let it be a File Reference, now my problem occours. As soon as i add a project for which a file reference exists (in an other folder). resharper makes almost everything read from the other project and says, ambigous reference (Same namespace and Classname).
So it seems that resharper recognises that the file reference and the project i added are identical, but it doesn't recognise it in the highlighting. because in the project i didn't add a project reference, because i already have a File reference.

Something to clarification, I don't reference in the file Reference the direct output of the other project, but a seperate folder to which i copy the output dll's in a postbuild step, because of locking problems. but with the AssmblyVersion, and Dll'name it should be recognisable that it is the same dll. in resharper 1.5 this worked, and visual studio although has no problems compiling it.

Sincerly

Thomas Stocker

3 comments
Comment actions Permalink

Hello Thomas,

are those types marked as ambiguous references shown duplicated in the 'Go
To Type' feature (Ctrl+N)?
Also, ReSharper associates projects and assemblies using the output assembly
name property of the project (Project|Properties) - are the values of those
properties equal to the names of the assemblies you really reference?

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I have the following problem with resharper.

I have one big solution to which I add from time to time other
projects for debugging. I do not change the reference to project
reference but instead i let it be a File Reference, now my problem
occours. As soon as i add a project for which a file reference exists
(in an other folder). resharper makes almost everything read from the
other project and says, ambigous reference (Same namespace and
Classname).

So it seems that resharper recognises that the file reference and the
project i added are identical, but it doesn't recognise it in the
highlighting. because in the project i didn't add a project reference,
because i already have a File reference.

Something to clarification, I don't reference in the file Reference
the direct output of the other project, but a seperate folder to which
i copy the output dll's in a postbuild step, because of locking
problems. but with the AssmblyVersion, and Dll'name it should be
recognisable that it is the same dll. in resharper 1.5 this worked,
and visual studio although has no problems compiling it.

Sincerly

Thomas Stocker



0
Comment actions Permalink

Dimitry,

I'm having the same problem. The answers to your questions are as followed:

1. The types DO show up twice in the 'Go To Type' feature.

2. I checked the project names and they appear to be identical to the generated assembly names that are referenced.

Thanks,
Dan

0
Comment actions Permalink

1. I have the same problem In the Go To Type they appear two times, the first one jumps to the Object Browser reference, and the second one jumps to the Source Code.

2. They are identical

Assembly Reference.

Copy Local is set to true:
C:\Program Files\PROCOS.NET\PROCOS.EOF.Shared.dll

Reference in the project:

]]>

Settings of the Project for this assembly

Assembly Name: PROCOS.EOF.Shared
Output Type : Class Library
Default Namespace: PROCOS.Components.EOF.Share
Project File: PROCOS.EOF.Shared.csproj
Project Folder:D:\Daten\NET_Mainline\Components\EOF\Shared\Project\
Output File: PROCOS.EOF.Shared.dll

This Errors ocour under Visual Studio 2003 with resharper 2.0.233.32

And other error that goes into the same category is that in the project that it doesn't recoginze properly i get the error on all class.

Duplicate definition '....' possible partial keyword missing,

Could this problems occour of the assembly key folder. With resharper version 2.0.229 it seems to work.

Sincerly Thomas Stocker.

P.S.: When i only have project references for all the projects in my solution it works

Message was edited by:
Thomas Stocker

0

Please sign in to leave a comment.