formatting-the-output-of-a-custom-build-step-or-build-event.md

description	title	ms.date	helpviewer_keywords	ms.assetid
Learn more about: Formatting the Output of a Custom Build Step or Build Event	Formatting the Output of a Custom Build Step or Build Event	08/27/2018	builds [C++], build events custom build steps [C++], output format events [C++], build build events [C++], output format build steps [C++], output format builds [C++], custom build steps	92ad3e38-24d7-4b89-90e6-5a16f5f998da

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} : [ any text ] {error | warning} code+number:localizable string [ any text ]

Where:

• {a | b} is a choice of either a or b.

• [item] is an optional string or parameter.

• Bold represents a literal.

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