3rd Party References?

Question

0.00/5 (No votes)

See more:

I have three Visual Studio solutions. One solution/project (Project1) defines an interface (IChokable, say). The second solution/project (Project2) contains a a class which creates an object (fooChicken) which implements IChokable. So Project2 has to have a reference to Project1, I get that.

In a third solution/project (Project3), I create a fooChicken object. So Project3 must contain a reference to Project2, I get that.

HOWEVER - this won't compile. It complains that Project3 must ALSO contain a reference to Project1, even though Project3 never tries to access any of the elements of IChokable on the fooChicken object.

Am I just doing this wrong? Do I really have to have a reference in every project to every project referenced by every other project? This strikes me as wrong. And not really doable. What if the app from Project3 existed in the world already, and I updated the objects from Project2 to contain new references, and shipped them? Would those Project3 objects stop functioning?

Surely I am missing something here. Is this just a debugging preference by Visual Studio?

Posted 25-Jun-14 18:03pm

JoeRip

Add a Solution

Comments

Prasad Avunoori 26-Jun-14 0:32am

Do you have 3 solutions? or 1 solution with 3 projects?

JoeRip 26-Jun-14 0:46am

Actually, 2 solutions: 1 with Project 1, and 1 with Projects2 and 3. I started to break the third project out to see if that mattered, but got distracted... why?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Snesh Prajapati · Answer 1 · 2014-06-25T18:30:00

You must have to add the dependencies of Project 2 (that mean Project 1) in order to work with it. Since project 2 has definition of fooChicken but it uses/implements interface (IChokable) defined in project 1 so you need to add it to Project 3.

There is nothing wrong here, it is simple and we encounter it very often, to use any DLL we must add all of its dependencies.

When you create a DLL...it is extremely important that you identify exactly what dependencies your application requires, and their versions. You must provide details of the dependencies in metadata of DLL or in read me file (instructions/ how to use).

For a real life example, please have a look at below link (and for more dig into the codebase of Microsoft Enterprise Library).
http://msdn.microsoft.com/en-us/library/ff647601.aspx[^]

Hope this will help. Thanks.