How to handle dependency libraries that my code doesn’t refer to, but should be in the basket?

Question

I am developing a number of plug-ins for the application of the third part, and the supplier provides us with all my plug-in assemblies along with some auxiliary assemblies for working with their system.

Our code usually refers to these helper assemblies, but their plugin assemblies still need to be copied to the external bin / debug or bin / release directory. Normally, I would do this event after the build in the main project, but since this project is a set of separate projects with their dependencies, I’m not sure what to do.

What are some recommendations (or recommendations) for handling this situation in Visual Studio?

Answer 1

Add the DLLs to your project in a folder with a descriptive name (libs, third-party, etc.).

Set the Copy to Output Directory (F4) property for them to Copy if Newer or Copy Always .