Best practices for referencing 3rd party assemblies

Question

I have been wondering what are best practices when it comes to referencing 3rd party assemblies. A while ago I asked a question \"Dependencies and references: what exactly shoul

Answer 1

You can also use NDepend to know and control exactly what you use from tiers library. I wrote an article about this Controlling the usage of libraries

Answer 2

An alternate I've been using on many (C#) projects is:

• Make a "Bin" folder in the solution directory (same level as the project directories)
• Make the output of all projects ../Bin instead of bin/debug or bin/release
• Put whatever files that are not a result of the build in "Bin", including library dependencies, certain data files or whatever, depending on the project
• Contents of "Bin" also goes to source control (without the build output, of course)
• Whatever libraries directly referenced by your projects goes to a "References" or "Libs" folder (sometimes I've also tried putting them in Bin too, but in this case you need to remember to disable copying of references to output dir when adding the reference to your project, which becomes tedious on large projects)

Not really sure if it's a good solution, but has worked for me till now.

Answer 3

If i have to deal with libraries that aren't registered in the GAC, I use the following method:

• Make a folder "Libs" with all third party libraries and their dependencies in it
• Reference the ones I need
• Create a post-build action that copies all the files in the "Libs" folder to the "bin/debug" (or release) folder

If you don't know the dependencies, you can use Dependency Walker.