Dll reference question

Question

0.00/5 (No votes)

See more:

Hi all,
this might be a simple one but I'll giev it a try ;)

Imagine the following dll strcture:

dll1
dll2
dll3

dll1 references dll2

dll3 references dll1

when I compile dll3 the compiler always want's me to also reference dll2.

Isn't that somehow passed with the references in dll1 (it references dll2 already)

Can this be avoided or is there a reason for this behavior?

best regards
Andy

Posted 21-Jan-11 2:50am

hoernchenmeister

Add a Solution

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)

Nish Nishant · Accepted Answer · 2011-01-21T03:10:00

Solution 1

Unless DLL3 uses a type from DLL2 directly, there is no need to reference DLL2 from DLL3. What is the exact error message the compiler gives you?

[Updated]
------------
Okay, this is in response to your comment. What's happening is that DLL1 exposes a public method or property that uses an interface defined in DLL2. Now since DLL3 has a reference to DLL1, even if it does not use this method/property/interface, it still needs to be able to resolve all public members in all types defined in DLL1. Thus DLL3 will need a reference to DLL2.

Posted 21-Jan-11 3:10am

Nish Nishant

Updated 21-Jan-11 3:30am

v3

Comments

hoernchenmeister 21-Jan-11 9:23am

The error is the following (sorry, I translated it...)
The type "library.Contracts.Core.Application.IEnvironmentProvider" is defined in a not referenced assembly. Add a reference to assembly "library.Contracts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"

Its all about an interface there...

Nish Nishant 21-Jan-11 9:29am

Ok, that makes sense now. I have updated my asnwer.

hoernchenmeister 21-Jan-11 9:33am

Thanks a lot for explaining this to me, it makes perfectly sense!
Have a great day and thanks again,
best regards
Andy

Nish Nishant 21-Jan-11 9:35am

You're welcome. You have a great day too.

Nish Nishant 21-Jan-11 13:17pm

Thank you, Kryukov!

Sergey Alexandrovich Kryukov 21-Jan-11 13:16pm

Very good answer - my 5.
--SA

Nish Nishant 21-Jan-11 13:18pm

Thank you, Kryukov! (my thanks keep appearing under the wrong comment node)