Skip to main content
BuyLog In
XAF: Cross-Platform .NET App UI & Web API
Search in…
Docs > Debugging, Testing and Error Handling > Debug, Collect and Analyze the Diagnostic Information
All docs
V24.2
.NET 8.0+
XAF: Cross-Platform .NET App UI & Web API
.NET Support and Migration
Getting Started
Installation, Upgrade, Version History
Backend Web API Service
UI Shell and Base Infrastructure
Storage, ORM, and Business Model Design
Data Manipulation and Business Logic
User Interface and Behavior Customization
Data Filtering
Application Security and Data Safety
Multi-Tenancy (Data per Tenant)
Validation (Prevent Data Errors)
Conditional Appearance (Manage State of UI Elements)
Reporting (Shape, Export & Print Data)
Analytics (Extract Data Insights)
Document Management
Business Process Management
Event Planning
Localization
Accessibility Support
Debugging, Testing and Error Handling
Debug, Collect and Analyze the Diagnostic Information
Log Files
Automatic Code Error Diagnostics
Unit Tests
End-to-End (Functional) Tests
Performance Optimization
Error Handling in ASP.NET Core Blazor and Web Forms
Hot Reload Support (ASP.NET Core Blazor)
Deployment
Support, QA & Troubleshooting
API Reference
Download CHM

Debug, Collect and Analyze the Diagnostic Information

  • 2 minutes to read

XAF applications support collecting diagnostic information using common approaches applicable to any .NET applications. This topic lists Visual Studio settings required to collect error information and describes how to analyze this information.

.NET Exceptions (Server-Side) for WinForms and ASP.NET

Adjust Visual Studio Settings

Before debugging an error, modify the following Visual Studio settings:

  • Click Tools | Options… to invoke the Options dialog. In the left-hand panel, choose the Debugging | General category and disable the Just My Code option.

    Debug_JustMyCode

  • Enable Common Language Runtime Exceptions in the Exception Settings window. If this window is hidden, click Debug | Windows | Exception Settings in Visual Studio’s menu (see Managing Exceptions with the Debugger).

    Debug_ClrExceptions2015

Analyze the Diagnostic Information

You can now run your application and reproduce the error. Open the Call Stack window and view the routines that are currently in the stack.

  • If the routines at the top of the call stack refer to .NET Framework or third-party libraries, you can search for the error message and call stack text in public community resources like Stack Overflow, where possible solutions may already be discussed.
  • If there are DevExpress routines at the top of the call stack, contact the DevExpress support team. Attach your project, the eXpressAppFramework.log file, the full exception call stack and inner exceptions info to the support ticket. If the error relates to your database content, attach a backup of the database as well.

JavaScript Exceptions (Client-Side) for ASP.NET

You can use the Developer Tools to trace client-side errors and get more information about them. Refer to the following help topic for more details: Diagnose Client-Side Errors.

Debugging

See Also