Since build 232, this problem of having Ambigous References and Duplicate
Definitions has been a real problem and has not diminished in any way for me
as some others have expressed with later versions. For some reason,
Resharper thinks I have two versions of the same class. I have another lib
directory that is in the parent directory where I have another copy of the
assembly for other purposes that I have a reference to. This was not a
problem with build 232 or Resharper vs2003. I am referencing the same
assembly that is in my \bin\debug folder, and for some reason Resharper
thinks it is different even though they are the same. I hope this is not
working as designed, because then I can't reference the same assembly in
another directory without Resharper thinking I have two different
assemblies when they are really the same exact thing (The classes are
identical).

This is allegedly fixed in the next build (237), just FYI.

"Kent Roylance" <roylance3@comcast.net> wrote in message
news:e2ikjl\$gm9\$1@is.intellij.net...

Since build 232, this problem of having Ambigous References and Duplicate
Definitions has been a real problem and has not diminished in any way for
me as some others have expressed with later versions. For some reason,
Resharper thinks I have two versions of the same class. I have another
lib directory that is in the parent directory where I have another copy of
the assembly for other purposes that I have a reference to. This was not
a problem with build 232 or Resharper vs2003. I am referencing the same
assembly that is in my \bin\debug folder, and for some reason Resharper
thinks it is different even though they are the same. I hope this is not
working as designed, because then I can't reference the same assembly in
another directory without Resharper thinking I have two different
assemblies when they are really the same exact thing (The classes are
identical).

Kent,
do I understand correctly that you have two copies of the same assembly
and you reference both copies in one of your projects?

Dmitry

Kent Roylance wrote:

Since build 232, this problem of having Ambigous References and Duplicate
Definitions has been a real problem and has not diminished in any way for me
as some others have expressed with later versions. For some reason,
Resharper thinks I have two versions of the same class. I have another lib
directory that is in the parent directory where I have another copy of the
assembly for other purposes that I have a reference to. This was not a
problem with build 232 or Resharper vs2003. I am referencing the same
assembly that is in my \bin\debug folder, and for some reason Resharper
thinks it is different even though they are the same. I hope this is not
working as designed, because then I can't reference the same assembly in
another directory without Resharper thinking I have two different
assemblies when they are really the same exact thing (The classes are
identical).

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

I get this all the time while I developing a VSTO project. The attached
image is taken from the ThisApplication.cs file. At the top of my file cs
file I have created a
using MSOutlook = Microsoft.Office.Interop.Outlook;

If I pull out the the using statement I don't get the ambigious references
any more. I have noticed that this happens only in the ThisApplication.cs
file. All other files will allow the using statement and not show the
ambigious usage. I also get a "Cannot convert source type "" to "" error
underlining while using the namespace alias. If I get rid of the alias, the
"error" goes away.

Regards,

"Dmitry Lomov (JetBrains)" <dmitry.lomov@jetbrains.com> wrote in message
news:e2kjet\$apd\$1@is.intellij.net...

Kent,
do I understand correctly that you have two copies of the same assembly
and you reference both copies in one of your projects?

>

Dmitry

>

Kent Roylance wrote:

>> Since build 232, this problem of having Ambigous References and Duplicate
>> Definitions has been a real problem and has not diminished in any way for
>> me
>> as some others have expressed with later versions. For some reason,
>> Resharper thinks I have two versions of the same class. I have another
>> lib
>> directory that is in the parent directory where I have another copy of
>> the
>> assembly for other purposes that I have a reference to. This was not a
>> problem with build 232 or Resharper vs2003. I am referencing the same
>> assembly that is in my \bin\debug folder, and for some reason Resharper
>> thinks it is different even though they are the same. I hope this is not
>> working as designed, because then I can't reference the same assembly in
>> another directory without Resharper thinking I have two different
>> assemblies when they are really the same exact thing (The classes are
>> identical).
>>
>>
>
>

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