Suggestion: Help me diagnose issues causing "This project is out of date" message
3/24/2011 10:10:12 AM
In my C++ build I often attempt to debug (F5) and am hit unexpectedly with the "This project is out of date: myproject - Debug Win32" message box.
This can show up due to a variety of reasons such as:
* A source or header file changed and object code needs to be rebuilt. (the usual, normal reason for the message)
* There is a header erroneously listed in the project filters. ie. a dev deleted a file but forgot to remove it from the filters.
* There is a generated header file which needs to be created.
* Other unexpected issues with the solution.
I'm in a situation right now where this message shows EVERY time I attempt to debug even though I just built the project and all the files seems to be in-place and have the correct time stamp.
So... I'm stuck. I would like a link or button next to each entry in the list on the "This project is out of date" dialog labeled something like "Why is it out of date?" or "Show Me" or "Details..." and it would show me why msbuild/VS feels the need to rebuild my project.
example output I'd appreciate:
"File: C:\foo\bar.h not found. Possibly a generated header file?"
"File: C:\foo\bar.cpp newer than C:\foo\int\bar.obj"
"File C:\foot\bar.h modified"
You get the picture I hope. This way, I can try and fix a problem if I keep getting this message unexpectedly.
If the UI is unchangeable, I would LOVE it if there could be a VS Extension which does the same rule evaluation and creates a report with the same information.