Raygun4net Versions Save

Raygun provider for .NET

v5.14.0

7 months ago

This 'release' wraps up several small changes, which unfortunately did not have their own numbered Releases created here properly] There was no nuget package version 5.14.0 actually released. The may have been point releases of downstream packages (e.g., raygun4aspnet) however. Apologies' for the confusion.

What's Changed

New Contributors

Full Changelog: https://github.com/MindscapeHQ/raygun4net/compare/v5.13.0...v5.14.0

v5.13.0

7 months ago

Removed now unused support for hooking into Raygun's APM profiler sampling

v5.12.0

7 months ago

What's Changed

Full Changelog: https://github.com/MindscapeHQ/raygun4net/compare/v5.11.0...v5.12.0

v6.0.3

7 months ago

Removed some dead code related to the previous TLS upgrade work

Updating downstream packages (that use raygun4net )

Fixing some nuget deployment configuration issues

[This wraps up the changes 6.0.0 -6.0.3, which were preview releases]

v6.0.0

7 months ago

TLS 1.2 is a requirement of our event ingestion endpoint.

Changes:

  1. Automatic Enabling of TLS 1.2 on environments which previously required some manual configuration.

Removed

  1. Dropped support for some versions of dotnet. Notably 2.0-3.5 as they dont support TLS1.2

[This is the reason for the major version bump, and cascading version bumps for the dependent packages]

v5.11.0

3 years ago

Changes:

  • Refactored offline storage logic
    • Configure the max number of reports that can be stored (up to 64 error reports)
    • Error reports are tied to a single API key
    • Enable/disable offline storage through the RaygunSettings instance
  • Add: An internal logger for the Raygun client

v5.10.2

4 years ago

Cache the environment information upon first look up to avoid redundant work.

v5.9.0

4 years ago
  • Using a singleton HTTP Client
  • Null checks on Raygun Settings for the excluded status codes

v5.8.0

4 years ago

Any part of Raygun4Net that automatically sends exceptions will now add the "UnhandledException" tag just like other providers. This is used to distinguish uncaught exceptions (likely application crashes) vs exceptions sent from try/catch blocks. Currently applies to ASP .NET, MVC and WebAPI projects.

5.7.0

4 years ago

This update includes additional options through the RaygunClient and RaygunSettings to stop sensitive data being collected from HTTP requests and transmitted to Raygun.

You can now supply custom logic, through the implementation of a new interface IRaygunDataFilter, to remove sensitive information from the raw data of requests that is captured when generating a crash report. The update includes two implementations for filter XML and KeyValue data. An example for implementing an JSON filter can be found on our public site under the documentation section.

This update is available to the following providers:

  • Raygun4Net.WebAPI
  • Raygun4Net.MVC
  • Raygun4Net.ASPNETCore