What is the recommendation for adding a library reference in a project?

Question

When I need to add a reference towards a library, I've always been told to use the "add existing project" method, and referencing the project itself inside my solution.

But here in my new company, the use another method. They have a server which holds the compiled dll's, and keep versions of them so they can reference older versions when a change is too important to refactor older apps.

While I find this system really complicated (I guess there is a lot of work if a program pointing an older version of the dll is updated and needs some changes in this dll), they seem to find it pretty convenient.

What are the best practices for this? Linking the dll directly? Linking the project? And why? Any information is welcome!

Thanks in advance !

Answer 1

I usually take a copy of the compiled dll (if the source project is not available or if I don't need the source) and put it in a folder inside my solution, and then reference that. I check it in to source control along with my project.

I am of the opinion that you should be able to check out a project and build it directly from source control without having to go hunting dlls etc.