how to stop referencing to hidden dll in c#

Question

4.20/5 (2 votes)

See more:

Hi
I have a dll (for example A.dll) which references to an other dll( say B.dll), now when i use A.dll in my app, my application can also see B.dll,i want B.dll to be not reached to my app.
can any one say that how to make B.dll is only used by A.dll and should be out of reach to my app.

Thank you
Santhosh

Posted 14-Dec-13 21:08pm

Santhosh Kumar

Add a Solution

Comments

Sergey Alexandrovich Kryukov 15-Dec-13 3:25am

Pretty interesting question, I up-voted it and answered.
—SA

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-12-14T21:24:00

You can make B.DLL a private assembly to A.DLL. Please see: http://msdn.microsoft.com/en-us/library/windows/desktop/ff951638(v=vs.85).aspx[^].

Before going this way, thoroughly consider all implications, pro and contra. It will be harder to support, especially if eventually you decide to use B.DLL resources elsewhere. One alternative would be joining A.DLL and B.DLL in one assembly, another one just leaving things as is and ignoring the problem.

—SA