Incorrect Ambiguous reference error.

Resharper 2.0, VS2003.
Attached is error message that is inccorect.
The problem is:
Prog1(compile Dll1) and Proj2(Dll2) sits in Sol1. There PostBuildEvent target is set to D:\Temp.
Prog1 a has reference to Dll2 that is located in D:\Temp (Prog1 Reference Path is set to D:\Temp).

DocData class is located in Dll2 and being used by Prog1.
Prog1 can be built with no errors but resharper raise error that DocData has ambiguous reference, It seems like resharper parse Dll2 from 2 locations -
1. D:\temp (the right location) 2. Dll2 bin\debug folder.

Thanks, Aviad.



Attachment(s):
Ambigouous reference problem.GIF
3 comments
Comment actions Permalink

I would like to add that if Proj2 is removed from the solution and added again - the problem disappears. Close the solution and open it again - the problem returns.

0
Comment actions Permalink

Aviad,

This is a known issue in ReSharper 2.0 Beta
See
http://www.jetbrains.com/resharper/download/known_issues_20_beta.html ,
item 2

Friendly,
Dmitry

aviad ezra wrote:

Resharper 2.0, VS2003.
Attached is error message that is inccorect.
The problem is:
Prog1(compile Dll1) and Proj2(Dll2) sits in Sol1. There PostBuildEvent target is set to D:\Temp.
Prog1 a has reference to Dll2 that is located in D:\Temp (Prog1 Reference Path is set to D:\Temp).

DocData class is located in Dll2 and being used by Prog1.
Prog1 can be built with no errors but resharper raise error that DocData has ambiguous reference, It seems like resharper parse Dll2 from 2 locations -
1. D:\temp (the right location) 2. Dll2 bin\debug folder.

Thanks, Aviad.


------------------------------------------------------------------------



--
Dmitry Lomov
Senior Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop With Pleasure!"

0
Comment actions Permalink

I have tow libraries MyApp.DataSets.dll and MyApp.DataAdapters.dll which contains classes in the same namespace MyApp.Data. Any project in my solution that references both libraries generates this error, which means virtually all my projects.

Is there any chance to get a fix for this problem. It makes it almost impossible for me to work with the beta. Too many bogus errors to concentrate on the real work to do. I installed the beta 2 this morning and I am already thinking of uninstalling it.

0

Please sign in to leave a comment.