Log In
[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Report Server
[Collapse]eXpressApp Framework
 [Expand]Getting Started
  [Expand]Application Solution Components
  [Expand]Business Model Design
  [Expand]Application Model
  [Expand]UI Construction
  [Expand]Extend Functionality
  [Expand]Data Manipulation and Business Logic
  [Expand]Security System
  [Expand]System Module
  [Expand]Extra Modules
  [Collapse]Debugging and Error Handling
    Collect and Analyze the Diagnostic Information
    Log Files
    Add Custom Log Entries and Customize the Default Tracer Behavior
    Error Handling in ASP.NET Applications
  [Expand]Application Life Cycle
 [Expand]Design-Time Features
 [Expand]Functional Testing
 [Expand]Task-Based Help
  Frequently Asked Questions
 [Expand]API Reference
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Collect and Analyze the Diagnostic Information

This article describes techniques you can use to obtain full information (call stacks, inner exceptions) for faster troubleshooting when an exception occurs in your XAF application.

  • In the Visual Studio menu, click Tools | Options... to invoke the Options dialog. In the panel to the left, choose the Debugging | General category and disable the Just My Code option.

  • If you use Visual Studio 2013 or an earlier version, click Debug | Exceptions... in the menu and enable Common Language Runtime Exceptions in the invoked Exceptions window (see How to: Break When an Exception is Thrown).

  • If you use Visual Studio 2015+, enable Common Language Runtime Exceptions in the Exception Settings window. If this window is hidden, click Debug | Windows | Exception Settings in the Visual Studio menu (see Managing Exceptions with the Debugger).

  • In addition to the exception information provided by Visual Studio, you can analyze diagnostic messages in the eXpressAppFramework.log file (see Log Files).

It is also possible to step into DevExpress source code when debugging (see How can I debug DevExpress .NET source code using PDB files).

The actions above usually must help you to see the internal cause of an error and guide you on how to fix the issue on your side yourself. If the routines from the top of the error call stack refer to the .NET Framework or third-party libraries, it is helpful to search for the error message and call stack text in public community resources like Stack Overflow, because possible solutions may already be discussed.

If the additional error information does not help you to fix the issue on your side, or there are DevExpress routines at the top of the call stack, contact the DevExpress support team. Attach the full exception call stack and inner exceptions info along with your project to the support ticket. If the database is required to reproduce the error, attach the database backup as well. With that essential diagnostic information, the support team will be able to research the situation much faster and thus help you in the most efficient way.

Expanded See Also

How would you rate this topic?​​​​​​​