BugSplat Documents

.NET dotnet_crashreporting_bugsplat_small

Crash reporting from BugSplat makes it simple to track and analyze the crashes experienced by your users.

Use the crash data collected by BugSplat to prioritize fixes, track defects, and understand the stability of your software.

To learn more about BugSplat sign up for a free trial.

Overview

Before doing anything make sure to log in using your email address and download the BugSplat software development kit for .NET applications.

To get a feel for the BugSplat service before enabling your application, feel free to experiment with the myDotNetCrasher sample application, which is part of the BugSplat software development kit. You may also want to browse the .NET API documentation.

Enabling your application with BugSplat technology:

  • In a few simple steps, your .NET application can be modified to provide full debug information on the BugSplat website when it crashes.
    1. Add a reference to "BugSplatDotNet.Dll".
    2. Add a call to BugSplat.CrashReporter.Init and add the BugSplat exception handlers for the appropriate set of system exceptions. As shown in the myDotNetCrasher sample app, this takes just a few lines of code.

  • The initialization call requires three parameters: BugSplat database, application name and version. You supply the application name and version. The BugSplat database is created and selected on the Databases page. Typically, you will create a new database for each major release of your product.
    1. Add BsSndRpt.exe, BugSplatDotNet.dll, and BugSplatRC.dll to your application's installer
    2. Edit BugSplatRC.dll with Visual Studio if you wish to change the banner displayed when your application crashes.
    3. Add symbolic debug information to your release build.

    Note: To get symbolic stack reports, debug information (PDB files) nneeds to be uploaded to the BugSplat website along with your application’s executable files. Modify your build settings so that symbol files are created for Release builds, e.g.,

    buildNet2-e14105434665201

    buildNet3-11-e1410469012133

    Remember that after each build you should upload the new executable and pdb files. The myDotNetCrasher sample app uses a Visual Studio post build event to automate this step.

  • Finally, note that the Visual Studio debugger’s hosting process can interfere with BugSplat’s ability to resolve symbols; it should be disabled in your project’s debug settings when submitting crash reports that occur while debugging.

Test your application by forcing a crash, and then verify that crashes are posted and symbol names are resolved.