views:

79

answers:

2

I've got a .net solution (written in C++/CLI) which references some .dll projects as follows:

MainProject->ProjectA->ProbjectB
MainProject->ProjectB

Originally I'd referenced both ProjectA and ProjectB from MainProject which gave me the warnings as mentioned above.

I can remove the warnings by removing the reference to ProjectB from ProjectMain but it makes it less obvious that MainProject relies on ProjectB. Is this the right thing to do to get rid of the warnings?

+1  A: 

Yeah that's fine.

If you have ReSharper, you can view the dependency graph by right-clicking ProjectMain --> Project Hierarchy.

BlueRaja - Danny Pflughoeft
I'm using C++ ...isn't ReSharper for C#?
Jon Cage
@Jon: I thought Resharper was available for C++/CLI as well, but I guess it's not, sorry
BlueRaja - Danny Pflughoeft
+1  A: 

Speaking in general terms, a system of dependencies can be depicted by a directed graph where each node is a software component and each edge is a dependency. In my opinion, the more simplification that can be done to the graph, the better.

Reinderien
So you're arguing for just having the MP->A->B links?
Jon Cage
Yep. It seems simpler to me.
Reinderien