Geek Answers Handbook

Vs2010 Question about circular dependence

Visual Studio 2010 introduces odd behavior related to circular dependencies, and as far as I know, this is LYING; and I wonder if you can help me get around this or point out my ignorance.

Essentially, I have an assembly called REM that references nothing more than standard .NET DLLs, and also an assembly called COR that references .NET assemblies and some other projects in the solution (none of these REM links).

I want to have COR reference REM, but visual studio is complaining about circular dependency and I just can't figure out why.

Any help would be greatly appreciated.

Thanks, Clint.

+4
source share
2 answers

Make sure you clean and rebuild both projects (you can also try closing and reopening a project or solution, or even restart VS so that it reloads projects correctly).

If you cannot figure it out from VS, you can try using a decompiler to see what actually references the real DLL. (See, for example, Just Decompile by Telerik, available at the bottom of the page: http://www.telerik.com/download.aspx ) Open the DLL files, and you should be able to see each of them referencing.

+2
source

It turns out that although REM did not contain an explicit reference to COR; in the project dependencies dialog with the solution, it was found that REM depends on COR (goodness knows why). "Removing" this dependency resulted in the successful addition of a link.

Today I came across the same case - I had project A, which was previously refernciong B, but this link was later removed from the project - only to still linger in the Solution dependency list, generating a fake dependency.

0
source

More articles:


All Articles