3 out of 3 rated this helpful - Rate this topic

Debugger.Break Method

.NET Framework 4.5

Signals a breakpoint to an attached debugger.

Namespace: System.Diagnostics
Assembly: mscorlib (in mscorlib.dll)

static member Break : unit -> unit

Exceptions

Exception	Condition
SecurityException	The System.Security.Permissions.UIPermission is not set to break into the debugger.

Remarks

If no debugger is attached, users are asked if they want to attach a debugger. If yes, the debugger is started. If a debugger is attached, the debugger is signaled with a user breakpoint event, and the debugger suspends execution of the process just as if a debugger breakpoint had been hit.

Version Information

.NET Framework

Supported in: 4.5, 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Portable Class Library

Supported in: Portable Class Library

.NET for Windows Store apps

Supported in: Windows 8

.NET Framework Security

UIPermission
for permission to start a debugger. Associated enumeration: PermissionState.Unrestricted
SecurityPermission
for operating with unmanaged code. Associated enumeration: SecurityPermissionFlag.UnmanagedCode Security action: Demand.

Platforms

Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Reference

Debugger Class

System.Diagnostics Namespace

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)