End Google Ads 201810 - BS.net 01 --> Hey,

This is a question I've had for a while and we just worked around it, but our libraries have grown substantially and it is becoming a bit of a pain to deal with. Perhaps one of you can enlighten me.

Say I create a class library called LibraryA. LibraryA has a dependency on another project called LibraryB (it has a reference to this other project).

When LibraryA is built, it properly adds LibraryB to its output folder. However, if I now actually use LibraryA in an application (by adding a reference to it), LibraryB doesn't get included and everything goes up in flames, nobody spared. I am forced to add a reference to LibraryA and LibraryB for it to work properly.

If you add a reference to one of the standard .NET libraries, it automatically adds a reference to all its dependencies. Is there a way to reproduce this behaviour with our own libraries?