I have a situation where Project A refers to Project B which refers to Project C. Project C includes several additional files that are marked as content, copy always. When I build Project B these additional files appear in the output folder for Project B. When I build Project A the dll from Project B appears but not the dll or additional files from Project C.
This is a simple example and it's easy to add a direct reference from A to C but I'm working on a large project with a large number of projects and it is hard to keep track of all the additional files included in each so it wouldn't be obvious if one day someone added a reference from C to D. Is there any way to specify that files should be cascaded up through the referenced projects?
The additional files often need to be modified at deployment or runtime so it isn't practical to make them embedded resources.