Indirect references exception among VB.NET and C# projects in the same solution

Consider the following scenario: A solution contains three projects.
Project A (C#)
Project B (VB.NET)
Project C (VB.NET)

Project A references project C and so does Project B.
Project B also references Project A.

Now, when project A exposes a type of Project B and I attempt to use it from Project B I get the following compilation error (in project A):
Indirect reference is being made to assembly 'ProjectB', which contains 'ProjectB.MyClass'. Add a file reference to '.....\ProjectB.dll' to your project. This error could also be due to mixing a file reference with a project reference to assembly 'ProjectB. In this case, try replacing the file reference to 'ProjectB.dll' in project '1_App_Code' with a project reference to 'ProjectB'.

I tried to remove and reassign the references. Any ideas?

[924 byte] By [papadi] at [2007-12-28]
# 1

Hi, papadi,

I want to make sure I understand your issue here. You say that Project B references Project A, but also Project A is exposing types found in Project B (and therefore presumably is expected to know of the existence of Project B; i.e., reference it). The way you've described this sounds like you're trying to create a circular reference -- can you clarify?

--Matt--*

P.S. Also, in case I'm misunderstanding what you wrote and the problem is a different issue -- can you clarify which version of VS you are using? Versions before 2005 may encounter the "diamond reference problem" which was fixed in VS2005.

MatthewGertzMS at 2007-9-4 > top of Msdn Tech,Visual Basic,Visual Basic IDE...