could you please tell us where is the BaseDial class defined and how is that project/assembly referenced in the project containing the code with 'Ambiguous references' (i.e. is it a project reference or a reference to project's output assembly)? Also, does invoking 'Go To Type' (Ctrl-N) on the BaseDial class show two instances of the class and where does it navigate to for both of these instances? Thanks.
I am having issues with the latest ReSharper EAP builds on a specific project. For some reason ReSharper complains about an ambiguous reference when I use a type named BaseDal. However with ReSharper disabled the Visual Studio IDE does not complain about it.
I have tried to look for all the assemblies and the assemblies that these assemblies reference and there was only one type with the name BaseDal so I don't understand where it goes wrong with ReSharper. I have cleared the cache multiple times and deleted all the temporary files ReSharper uses.
sorry that I could not response sooner. The BaseDal is in a referenced external Assembly. Ctrl + N does not navigate to the BaseDal class. The strange part is that this only happens in the ReSharper intellisense. I have even tried this on a new machine, clean installation. Once ReSharper analyzes the project it will find more than one BaseDal for some reason.
I will try to create a small project and reproduce this tuesday as I am on sick leave now and I will send you the code so you can try it out for yourself. I believe that maybe it has to do with our BaseDal or the containing assembly as I have seen the same behaviour with other projects that also references this assembly.
could you please tell us where is the BaseDial class defined and how is that project/assembly referenced in the project containing the code with 'Ambiguous references' (i.e. is it a project reference or a reference to project's output assembly)? Also, does invoking 'Go To Type' (Ctrl-N) on the BaseDial class show two instances of the class and where does it navigate to for both of these instances? Thanks.
> >> I am having issues with the latest ReSharper EAP builds on a specific >> project. For some reason ReSharper complains about an ambiguous >> reference when I use a type named BaseDal. However with ReSharper >> disabled the Visual Studio IDE does not complain about it. >> >> I have tried to look for all the assemblies and the assemblies that >> these assemblies reference and there was only one type with the name >> BaseDal so I don't understand where it goes wrong with ReSharper. I >> have cleared the cache multiple times and deleted all the temporary >> files ReSharper uses. >> >> See the attached screenshots. >> >> Cheers >> >
I have tried several versions of ReSharper to see in what EAP build this was introduced and it was introduced in ReSharper EAP Build 254. When I install any other ReSharper EAP Build from 248 to 253 there is no problem but when I install ReSharper EAP Build from 254 up to 261 I get the same issue. I guess you guys know better than me what exactly changed from ReSharper EAP Build 253 to 254.
I have created a small project and referenced the DLL that is causing this but in my small project I don't have this issue with any build. So right now I had to revert back to ReSharper EAP Build 253 to be able to work with that specific project.
could you please tell us where is the BaseDial class defined and how is that project/assembly referenced in the project containing the code with 'Ambiguous references' (i.e. is it a project reference or a reference to project's output assembly)? Also, does invoking 'Go To Type' (Ctrl-N) on the BaseDial class show two instances of the class and where does it navigate to for both of these instances? Thanks.
> >> I am having issues with the latest ReSharper EAP builds on a specific >> project. For some reason ReSharper complains about an ambiguous >> reference when I use a type named BaseDal. However with ReSharper >> disabled the Visual Studio IDE does not complain about it. >> >> I have tried to look for all the assemblies and the assemblies that >> these assemblies reference and there was only one type with the name >> BaseDal so I don't understand where it goes wrong with ReSharper. I >> have cleared the cache multiple times and deleted all the temporary >> files ReSharper uses. >> >> See the attached screenshots. >> >> Cheers >> >
Hello Gabriel,
could you please tell us where is the BaseDial class defined and how is that
project/assembly
referenced in the project containing the code with 'Ambiguous references'
(i.e. is it a project reference
or a reference to project's output assembly)? Also, does invoking 'Go To
Type' (Ctrl-N) on the BaseDial class
show two instances of the class and where does it navigate to for both of
these instances? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello Dmitry
sorry that I could not response sooner. The BaseDal is in a referenced
external Assembly. Ctrl + N does not navigate to the BaseDal class. The
strange part is that this only happens in the ReSharper intellisense. I have
even tried this on a new machine, clean installation. Once ReSharper
analyzes the project it will find more than one BaseDal for some reason.
I will try to create a small project and reproduce this tuesday as I am on
sick leave now and I will send you the code so you can try it out for
yourself. I believe that maybe it has to do with our BaseDal or the
containing assembly as I have seen the same behaviour with other projects
that also references this assembly.
--
Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b6c388c89aecc0da490a@news.intellij.net...
>
>
>
>
>> I am having issues with the latest ReSharper EAP builds on a specific
>> project. For some reason ReSharper complains about an ambiguous
>> reference when I use a type named BaseDal. However with ReSharper
>> disabled the Visual Studio IDE does not complain about it.
>>
>> I have tried to look for all the assemblies and the assemblies that
>> these assemblies reference and there was only one type with the name
>> BaseDal so I don't understand where it goes wrong with ReSharper. I
>> have cleared the cache multiple times and deleted all the temporary
>> files ReSharper uses.
>>
>> See the attached screenshots.
>>
>> Cheers
>>
>
I have tried several versions of ReSharper to see in what EAP build this was
introduced and it was introduced in ReSharper EAP Build 254. When I install
any other ReSharper EAP Build from 248 to 253 there is no problem but when I
install ReSharper EAP Build from 254 up to 261 I get the same issue. I guess
you guys know better than me what exactly changed from ReSharper EAP Build
253 to 254.
I have created a small project and referenced the DLL that is causing this
but in my small project I don't have this issue with any build. So right now
I had to revert back to ReSharper EAP Build 253 to be able to work with that
specific project.
Cheers
Gabriel Lozano-Morán
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b6c388c89aecc0da490a@news.intellij.net...
>
>
>
>
>> I am having issues with the latest ReSharper EAP builds on a specific
>> project. For some reason ReSharper complains about an ambiguous
>> reference when I use a type named BaseDal. However with ReSharper
>> disabled the Visual Studio IDE does not complain about it.
>>
>> I have tried to look for all the assemblies and the assemblies that
>> these assemblies reference and there was only one type with the name
>> BaseDal so I don't understand where it goes wrong with ReSharper. I
>> have cleared the cache multiple times and deleted all the temporary
>> files ReSharper uses.
>>
>> See the attached screenshots.
>>
>> Cheers
>>
>