Formatting the Output of a Custom Build Step or Build Event
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

Formatting the Output of a Custom Build Step or Build Event

If the output of a custom build step or build event is formatted correctly, users get the following benefits:

  • Warnings and errors are counted in the Output window.
  • Output appears in the Task List window.
  • Clicking on the output in the Output window displays the appropriate topic.
  • F1 operations are enabled in the Task List window or Output window.

The format of the output should be:

{filename (line# [, column#]) | toolname} : 
  [anytext] {error | warning} code####: Localizable String
   [
      any text
   ]

Where:

  • {a | b} is a choice of either a or b.
  • [optional] is an optional parameter

For example:

C:\sourcefile.cpp(134) : error C2143: syntax error : missing ';' before '}'

LINK : fatal error LNK1104: cannot open file 'somelib.lib'

See Also

Understanding Custom Build Steps and Build Events

Show:
© 2016 Microsoft