How are these DLLs referenced???

I have inherrited a .NET solution and am trying to figure out how certain DLLs are making it into the bin directory when compiled even though they are not referenced.

Can anyone help me learn how this is happening? I need to include a new dll in the same manner as these are being included.

Thank you!
HangTenDesignAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
HangTenDesignConnect With a Mentor Author Commented:
I found a setting under Project --> [Project] Properties in Visual Studio called Build Events. The assemblies that are being pulled in are defined in the "Post Build Events" area. Once I added the same command line there, the DLLs got copied to the other Projects bin directory without the referrence. This is how the others were set up as well.

Thanks all for your input but I found this on my own.
0
 
WilliamCommented:
If you have an assembly that references 'another' asssembly it will be pulled in... You can also set them to be copied local:true|false
0
 
Jaime OlivaresSoftware ArchitectCommented:
also them could be declared as dependencies.
0
 
JuckManCommented:
If you are using VS the right click on references folder and select "Add references". This will add the selected assembly in to your project and that assembly will be copied in to your bin folder.

If you add reference to a assembly which is in the GAC then that assembly by default would not be copied to your bin folder. (called shared assembles). If is not in GAC (called private assemblies) then a copy will be made in to the bin folder. This architecture is to support XCOPY deployment.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.