Resolving Resources dependency in c#

Question

0.00/5 (No votes)

See more:

Hello sir,
I am very happy with code project because it a platform where we get solution of almost all question whether good or bad.
sometimes i ask question but after getting answer i felt it was very stupid question we should not ask .so i am very great full towards code project team to ignore my stupidity.

Here my doubt is
I am creating a class library project say (Custom_Server) in c# that needs reference of Utility dll.
so at the time of deployment presence of utility dll is needed or Custm_Server dll
is sufficient because it already has reference of Utility dll.

Posted 6-Sep-12 21:23pm

raghubansh kumar

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)

Philip Stuyck · Answer 1 · 2012-09-06T22:07:00

No you need both the utility dll and the custom server dll.
The references you add in visual studio is just to make clear to visual studio that you will be using that dll, it improves the intellisense, enables you to put in a type and then to let visual studio find out in which namespace it is to add the using clause. Without the reference, VS just does not know all this and the project would not even compile, because then VS would see a lot of unknown types.
At runtime, the reference is still there and the presence of the dll is very much needed.
Don't confuse the .NET dll's with lib's like in c or c++, they are not linked together into one assembly wherein everything is resolved, they are genuine dll's, ie dynamically linked.