Learn more about how Sentry's .NET SDK works with Windows Presentation Foundation (WPF) applications.

Sentry's .NET SDK works with Windows Presentation Foundation applications through the Sentry NuGet package. It works with WPF apps running on .NET Framework 4.6.1, .NET Core 3.0 or higher.

Install the NuGet package to add the Sentry dependency:

dotnet add package Sentry -v 4.7.0

In addition to initializing the SDK with SentrySdk.Init, you must configure the WPF specific error handler.

The SDK should be initialized in the constructor of your application class (usually App.xaml.cs). Do not initialize the SDK in the OnStartup() event of the application or the Hub will not be initialized correctly.

The SDK automatically handles AppDomain.UnhandledException. On WPF, for production apps (when no debugger is attached), WPF catches exception to show the dialog to the user. You can also configure your app to capture those exceptions before the dialog shows up:

using System.Windows;

public partial class App : Application
    public App()
        SentrySdk.Init(options =>
            // Tells which project in Sentry to send events to:
            options.Dsn = "https://examplePublicKey@o0.ingest.sentry.io/0";

            // When configuring for the first time, to see what the SDK is doing:
            options.Debug = true;

            // Set traces_sample_rate to 1.0 to capture 100% of transactions for tracing.
            // We recommend adjusting this value in production.
            options.TracesSampleRate = 1.0;

            // Enable Global Mode since this is a client app
            options.IsGlobalModeEnabled = true;

            //TODO: any other options you need go here
        DispatcherUnhandledException += App_DispatcherUnhandledException;

    void App_DispatcherUnhandledException(object sender, DispatcherUnhandledExceptionEventArgs e)

        // If you want to avoid the application from crashing:
        e.Handled = true;
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").