BugSplat 8.6.2

BugSplat for .NET on Windows

Crash reporting for .NET 10 and .NET Framework 4.7.2+ apps on Windows, through the BugSplat native SDK. Crashes and handled exceptions are reported as minidumps, which BugSplat symbolicates from your uploaded symbols. Managed frames get file names and line numbers without you shipping PDBs.

Install

dotnet add package BugSplat

The package includes BugSplat's native runtime for x86, x64 and ARM64. At build time it copies the set that matches your app's architecture next to the executable: BugSplat.dll, BugSplatMonitor.exe, BugSplatRc.dll and BugSplatWer.dll, plus their PDBs. They must ship with your app. The monitor is a separate process that writes and uploads the report after a crash.

Use

using BugSplatDotNet;

var bugSplat = new BugSplat("YourDatabase", "YourApp", "1.0.0");

// Unhandled exceptions and native faults are now reported automatically.

try
{
    DoWork();
}
catch (Exception ex)
{
    // Call from inside the catch: the dump is taken at the throw site.
    bugSplat.Post(ex);
}

Upload your app's .exe, .dll and .pdb files to BugSplat with symbol-upload so reports show function names, files and line numbers. Build with <DebugType>full</DebugType> (Windows PDBs).

Architecture

The native runtime must match the architecture your process runs as. It is chosen from, in order:

1. RuntimeIdentifier, for example win-arm64.
2. PlatformTarget (x86, x64 or ARM64).
3. For .NET AnyCPU, the architecture of the .NET SDK doing the build. That is also what the app's .exe runs as.
4. For .NET Framework AnyCPU with Prefer32Bit, x86. Otherwise x64.

To override the choice, set <BugSplatNativeArchitecture>x86|x64|arm64</BugSplatNativeArchitecture>.

The files are copied for executables and test projects. A library loaded by a native host (a plugin, or a CLR hosted from C++) can set <BugSplatCopyNativeFiles>true</BugSplatCopyNativeFiles>. The files must then be deployed next to the host's executable, because that is where BugSplatMonitor.exe is looked for.

Run the app through its .exe. dotnet YourApp.dll makes dotnet.exe the process, and the monitor won't be found next to it.

Learn more

• BugSplat documentation
• Samples and source