Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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
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.