visual studio - Managing optional dll dependencies in net core

Question

I have a solution targeting "netcoreapp3.1" consisting of main project, and multiple optional libraries. For debugging purposes right now the main project has dependencies to all the libraries, this ensures that then the main project is rebuild, the libraries dll's are rebuild too and new dll's are copied to main projects output folder. But if i delete an optional dll, the main solution gives an error "An assembly specified in the application dependencies manifest was not found". Obiously, if i delete the dependencies and manually copy dlls from libraries output, everything works as intended, but I'm afraid that this will be prone to human error. Is there better solution? Maybe some way to mark dependency as optional? Or maybe some other option to build and copy library dlls then the main project is rebuild?

question from:https://stackoverflow.com/questions/66060380/managing-optional-dll-dependencies-in-net-core

Answer 1

Waitting for answers