locked
How to view build log in VS2010? RRS feed

  • Question

  • With earlier versions of Visual C++, you could view the build log by ctrl+clicking the link in the output window or opening it directly from the intermediate folder. With VS2010 Beta 1 this doesn't seem to exist. Have I missed it? There is a .log file written to the solution folder, but it just contains the same things as the output window, and doesn't show the command lines used. I need this to debug why something isn't building correctly.
    Thursday, June 18, 2009 10:19 AM

Answers

  • The old HTML log output option is no longer available - we use the command MSBuild logging instead. What you need to do is go to Tools->Options->Projects and Solutions->Build and Run. At the bottom, change the logging level from Normal to Detailed for either the output window or log file.

    This will generate a considerable amount of information about the overall build process - so what I do is then just click in the output window and search for cl.exe, or whatever the name of the tool is you are looking for.
    VS Project Team http://blogs.msdn.com/vsproject
    Saturday, June 20, 2009 9:38 PM

All replies

  • The old HTML log output option is no longer available - we use the command MSBuild logging instead. What you need to do is go to Tools->Options->Projects and Solutions->Build and Run. At the bottom, change the logging level from Normal to Detailed for either the output window or log file.

    This will generate a considerable amount of information about the overall build process - so what I do is then just click in the output window and search for cl.exe, or whatever the name of the tool is you are looking for.
    VS Project Team http://blogs.msdn.com/vsproject
    Saturday, June 20, 2009 9:38 PM
  • Thanks Brian. Upping those seems like a reasonable compromise. I have to say though, this is clearly more hassle than it was in VS2005. There's no handy link to open the log file, instead you have to browse about in Windows Explorer; and under the default "minimal" verbosity, error output from custom build rule executables isn't displayed at all. Instead you get cryptic messages about cmd.exe exiting. I guess I'll stick these up on Connect.
    Monday, June 22, 2009 12:59 PM
  • Definately file up Connect issues and if possible, try to give as much detail about your thoughts on what would be the most valuable.

    You would not believe the amount of debate that has gone on with regards to how much information to put into the logs - especially minimal and normal. It has changed wildly over the coarse of VS 2010 development. Obviously I can promise any changes, but the more detailed feedback - even "I was looking for information XYZ" - the more likely we can tune the log.
    VS Project Team http://blogs.msdn.com/vsproject
    Tuesday, June 23, 2009 3:29 AM
  • Definately file up Connect issues and if possible, try to give as much detail about your thoughts on what would be the most valuable.

    You would not believe the amount of debate that has gone on with regards to how much information to put into the logs - especially minimal and normal. It has changed wildly over the coarse of VS 2010 development. Obviously I can promise any changes, but the more detailed feedback - even "I was looking for information XYZ" - the more likely we can tune the log.
    VS Project Team http://blogs.msdn.com/vsproject

    Thanks. Now I know how to realize the function.
    Monday, July 26, 2010 8:44 AM