I have a startup project "A" (.exe) with a explicit reference to a project "B". Project "C" is NOT referenced directly by project "A" or indirectly by project "B".
When starting an instance of project "A" (F5), then project "B" is build upfront, but project "C" is not.
Is it possible to force Visual Studio to build project "C" anyway? I am using ReSharper Build, so a solution with ReSharper would be fine.
I don't wan't to add a explicit project reference to project "C". It is loaded implicitly via reflection (why is not the question).
What I already tried:
- Change Visual Studio setting in "Projects and Solutions --> Build and Run --> On Run, when projects are out of date:" to "Always build"
- Selected project "C" in ReSharper setting "Tools --> Build --> Heuristics --> Projects that should ALWAYS be built:"