Do they exist or I need to read billions of lines of /verbosity:diag parameter lines? Maybe you have other solutions?
+1
A:
The MSBuild Sidekick has some debugging functionality along with some other good stuff.
Sayed Ibrahim Hashimi
2010-03-18 14:39:45
And the license isn't so expensive if you want to use it on your own. (50 bucks). But for enterprise use it's almost 2k $ so I don't think that many enterprises will but it for his developers.
Leszek Wachowicz
2010-03-25 14:45:04
A:
The output logs are the primary tool for diagnosing problems with MSBuild scripts and they will pretty much give you all the details you might need. If you are tracing a specific problem, you can lower the verbosity level and add some explicit information messages to your build:
<Message Importance="normal" Text="Some diagnostic info incl. property values" />
You can do real debuging if you write custom build steps and attach to the MSBuild binary.
First of all though, what is the real problem you have. Understanding what you are trying to achieve and where you encounter problems might help.
I would also recommend reading Inside the Microsoft® Build Engine: Using MSBuild and Team Foundation Build - this book should give you plenty of answers that should stop you from having to diagnose the project in the first place.
mfloryan
2010-03-19 10:54:02