Skip to content

Added docs explaining how to disable Sentry Native in the .NET SDK #15293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 23, 2025
Merged

Added docs explaining how to disable Sentry Native in the .NET SDK #15293

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
baa179f
Update disable-integrations.mdx
jamescrosswell Oct 23, 2025
6bf3a21
Update disable-integrations.mdx
jamescrosswell Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion docs/platforms/dotnet/common/configuration/disable-integrations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@ description: "Learn more about the methods that disable integrations."

All of Sentry’s SDKs provide integrations, which extend functionality of the SDK. Most integrations are enabled by default, though you can disable them if needed.

To disable an integration, for example, the automatic capture of unhandled exceptions:
# Options

Most integrations can be disabled via the options when initializing the SDK. For example, to disable the automatic capture of unhandled exceptions:

```csharp
// Add it to your Sentry SDK initialization block:
Expand Down Expand Up @@ -39,3 +41,15 @@ Disables adding the list of .NET Frameworks installations into events.
## DisableAppDomainProcessExitFlush

Disables flushing events upon `AppDomain.ProcessExit` event handler.

# Sentry Native

On many platforms, the .NET SDK for Sentry includes Sentry Native, which lets you capture crash reports for native (unmanaged) code. If you are experiencing difficulties, you can disable Sentry Native by setting the `SentryNative` build property to `false`:

```xml
<PropertyGroup>
<SentryNative>false</SentryNative>
</PropertyGroup>
```

Note: Sentry Native is disabled by default for applications targeting WASM.
Loading