The Debugging section gives you access to all the settings related to the Debugger functionality, such as behavior of breakpoints, the Output panel and much more.


The first block in the Debugging section of the Options menu helps you to set all the main parameters for the debugging functionality. Here you can manage:

  • behavior of breakpoints:
    • if TWS should ask before deleting all breakpoints,
    • if TWS should break all processes when one process breaks,
    • if TWS should break when it catches an exception,
    • enable / disable breakpoints filters,
  • the process of debugging:
    • enable / disable address-level debugging,
    • enable / disable Just My Code,
    • enable / disable .NET Framework source stepping,
    • if TWS should step over properties and operators,
    • enable / disable source server support,
    • if TWS should warn if no symbols on launch,
    • if TWS should warn if script debugging is disabled on launch,
    • if TWS should load dll exports,
    • if TWS should use Managed Compatibility Mode,
  • work on exceptions, properties, and other settings:
    • enable / disable the exception assistant,
    • enable / disable property evaluation,
    • if TWS should highlight the entire source line for breakpoints and the current statement,
    • if TWS should require source files to exactly match the original version,
    • if TWS should show the raw structure of objects in variables windows,
    • if TWS should ignore GPU memory access exceptions if the written data didn't change the value.

Options menu - Debugging - General

Edit and Continue

The Edit and Continue block allows you to manage this feature — an ability to make changes in your code while TWS is in the debugging mode. Here you can enable / disable the Edit and Continue feature and set the native-only options, such as warn about stale code, allow precompilling, etc.

Options menu - Debugging - Edit and Continue

NB: As for now, the Edit and Continue feature is unavailable in The Welkin Suite. When you start debugging, TWS locks the files to prevent unpredictable changes.


This block gives you an ability to enable / disable the Just-In-Time debugging for such code types: managed, native, or script. This means that if an error occurs in such code outside The Welkin Suite, TWS will be launched and you can begin debugging.

Options menu - Debugging - Just-In-Time

NB: As for now, the Just-In-Time feature is unavailable in The Welkin Suite.

Output Window

Here you can set the behavior of the Output Panel during the debugging process. All the settings are divided into two blocks:

  • General Output Settings (you can only enable or disable them):
    • all debug output,
    • exception messages,
    • module load messages,
    • module symbol search messages,
    • module unload messages,
    • process exit messages,
    • step filtering messages,
    • thread exit messages,
  • WPF Trace Settings (you can set one of the variants: Off, Critical, Error, Warning, Information, Verbose, Activity, or All):
    • animation,
    • data binding,
    • dependency properties,
    • documents,
    • freezable,
    • HWND hosting,
    • markup,
    • name scope,
    • resource dictionary,
    • routed events.

Options menu - Debugging - Output Window

Below the list of settings you can see a tooltip about a selected setting. You can change the setting by selecting some necessary option from the drop-down list next to it or by double-clicking on it.


The last block in the Debugging section of the Options menu helps you to manage the symbols for the debugging process. Here you can set:

  • the location for symbols, and manage the list of the locations,
  • the directory for caching symbols, load the symbols, and empty the cache,
  • for which the part of symbols TWS should automatically load symbols: all modules or only specified, and specify such modules if needed.

Options menu - Debugging - Symbols

In this section:

This also may be useful:

Last modified: 2017/02/03 12:00

footer image