From: Support for conditional compilation symbols - #19 by tescosw
Ah, that one. It’s very odd, yeah. Neither me or Carlo could reproduce this; my gut feeling, from the log I saw, is seems me that somehow MSBuild doesn’t detect the dependencies between EBuild project references, and it somehow is building project B that depends on A, before A has finished (or started), IIRC.
Isn that’s the case, that bug should be hidden/worked around if you explicitly set dependencies inside the Solution file (BS has a dialog for that). you’d get sections like this in the .sln:
ProjectSection(ProjectDependencies) = postProject
{F8A2E4F6-C122-4A06-A27B-D77591E674CD} = {F8A2E4F6-C122-4A06-A27B-D77591E674CD}
{4D283143-C13F-478F-A328-485E98D22CF1} = {4D283143-C13F-478F-A328-485E98D22CF1}
EndProjectSection
Does that fix/hide the problem? If not, then the issue seems to be something else. I’ll review the other thread again as well.
- VS Dialog doesnt work for that, because references are already decalred in projects - the dialog and solution based references work only for references not decalred in projects. (Checks are already checked)
the cleaner/simpler a tests you could create where this fails for you (and a corresponding log), the better the chance that I can narrow this down w/o a local repro…
See the deatiled a diagnostic log files attachedmsbuildDiag.txt (403.4 KB) msbuildetailed.txt (168.6 KB)
The best i have.