MS-Build: Displaying out-of-date dependencies

Question

I'm trying to debug an MS-Build in VS2010 setup that reports about a half-dozen projects are out-of-date on every build. I'm trying to trawl through the diagnostic output for a clue to what files are consider out-of-date and causing the rebuild.

Is there a simpler way to display the reason for dependencies to avoid looking for a needle in the proverbial haystack?

thanks Dan

score 1 · Accepted Answer · edited May 23 '17 at 11:48

1

The answer to the question "VS2010 always thinks project is out of date but nothing has changed" shows you how to debug the dependencies checker of visual studio.

edited May 23 '17 at 11:48

Community

1
1

answered Mar 30 '12 at 08:26

hmuelner

8,093
1
28
39

Thanks for the response. That's exactly what I was after. – Dan G Aug 21 '12 at 00:03

MS-Build: Displaying out-of-date dependencies

1 Answers1