Skip to content

Commit 6f9c539

Browse files
authored
Update tracing-and-instrumenting-applications.md
1 parent fc44ef9 commit 6f9c539

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

docs/framework/debug-trace-profile/tracing-and-instrumenting-applications.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -127,9 +127,6 @@ System.Diagnostics.Debug.WriteLine("Hello World!");
127127

128128
You can produce custom results by implementing your own listener. A custom trace listener might, for example, display the messages to a message box, or connect to a database to add messages to a table. All custom listeners should support the six methods mentioned above. For more information on creating developer-defined listeners, see <xref:System.Diagnostics.TraceListener> in the .NET Framework reference.
129129

130-
> [!NOTE]
131-
> In Visual Basic 2005, the **Debug.Write**, **Debug.WriteIf**, **Debug.WriteLine**, and **Debug.WriteLineIf** methods have replaced the **Debug.Print** method that was available in earlier versions of Visual Basic.
132-
133130
The **Write** and **WriteLine** methods always write the text that you specify. **Assert**, **WriteIf**, and **WriteLineIf** require a Boolean argument that controls whether or not they write the specified text; they write the specified text only if the expression is **true** (for **WriteIf** and **WriteLineIf**), or **false** (for **Assert**). The **Fail** method always writes the specified text. For more information, see [How to: Add Trace Statements to Application Code](../../../docs/framework/debug-trace-profile/how-to-add-trace-statements-to-application-code.md) and the .NET Framework reference.
134131

135132
## Security Concerns

0 commit comments

Comments
 (0)