Do you know any guideline or if you have mastered your own way of reading the output window of the VS after a failed build to gather the most important notes in a shortest time?
Asked
Active
Viewed 201 times
0
-
4I speed things up by mainly ignoring it and using the Error List instead. – spender Nov 12 '10 at 10:29
-
Setting MSBuild output verbosity to minimal (Tools -> Options -> Projects and Solutions -> Build and Run) might help. – VladV Nov 12 '10 at 11:42
-
I set the font size really small so I can read everything important without abusing the scroll bar. – Cody Gray - on strike Nov 12 '10 at 11:54
1 Answers
2
well, may be the most efficient way to read build failures is the Error list window.
but may be it is useful to use the output window to track any exception occurred and handled implicitly, or to track any new loaded modules (assemblies).
or if you are using the build events, and there is a failure when running the dos commands, you can also see it in the output.
you can also write your own events to the output, using Debug.Write("");
and by the way, there are some frameworks (such as NHibernate) who log there events into the output window.

Nour
- 5,252
- 3
- 41
- 66