elmah.io changelog

We have open-sourced and published our Broken Links Checker for Azure DevOps. With this extension, you can automatically scan your code for links during a build and have Azure DevOps test all of those links. Get it on the Azure DevOps Marketplace here: https://marketplace.visualstudio.com/items?itemName=elmahio.broken-links-checker.

Here’s a quick example of YAML for running the checker:

steps:
- task: BrokenLinksChecker@0
  inputs:
    includeGlobs: |
      **/*.html
      **/*.cshtml
    excludeFileGlobs: |
      **/node_modules/**
    ignoreUrlPatterns: |
      example.com/*
    failOnBroken: true
    concurrency: 16
    timeoutMs: 10000
    allowedStatus: 200-299,301,302

https://blog.elmah.io/how-net-garbage-collector-works-and-when-you-should-care/

Learn how the .NET Garbage Collector works, manages memory automatically, and how to optimize your app's performance with GC best practices.

We’ve updated the two-factor authentication (2FA) implementation on elmah.io to improve both security and usability. The new version includes:

• Regenerated secrets for each setup. You now need to scan the QR code again whenever you re-enable 2FA.
• Streamlined enable/disable flow for a smoother user experience.
• One-time token validation to prevent reuse of old authentication codes.

To take advantage of the new implementation, we recommend disabling and then re-enabling 2FA on your account. When doing so, create a new account entry in your authenticator app, as previously stored entries will no longer work.

We now show a warning on the Profile page when your user is part of an organization but not marked as private. We recommend that everyone mark their user as private once it has been added to an organization. Users not marked as private will appear in the search results when adding users to an organization.

https://blog.elmah.io/hidden-costs-of-boxing-in-c-how-to-detect-and-avoid-them/

Learn how boxing and unboxing in C# impact performance through hidden heap allocations. See benchmarks and best practices to avoid overhead.

We released a new version (5.3.54) of the Serilog.Sinks.ElmahIo package. The new version includes the following changes:

• Exclude keys used by Elmah.Io.AspNetCore.Serilog from Data.
• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.
• Upgraded build image to Windows 2025.

We released a new version (5.3.43) of the Elmah.Io.Umbraco package. The new version includes the following changes:

• Updated Umbraco.Cms to 10.8.11 to avoid targeting a version with vulnerabilities.
• Newest Elmah.Io.* packages.
• General code improvements by fixing all code suggestions.

We released a new version (5.4.63) of the Elmah.Io.NLog package. The new version includes the following changes:

• Made an OnInstallation hook available in the target.
• Added TargetFrameworks net461 since net45 is not included in Visual Studio 2022 by default.
• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.
• Upgraded build image to Windows 2025.

We released a new version (5.3.44) of the Elmah.Io.Log4Net package. The new version includes the following changes:

• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.
• Upgraded build image to Windows 2025.

We released a new version (5.3.35) of the Elmah.Io.Heartbeats.Hangfire package. The new version includes the following changes:

• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.

We released a new version (5.3.32) of the Elmah.Io.Functions.Isolated package. The new version includes the following changes:

• Added more examples of configuring elmah.io in the .NET 9 sample.
• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.

We released a new version (5.4.45) of the Elmah.Io.Functions package. The new version includes the following changes:

• Added local.settings.json files to samples to show how to configure an app.
• Newest Elmah.Io.Client.

We released a new version (5.3.67) of the Elmah.Io.Extensions.Logging package. The new version includes the following changes:

• Added support for setting the Detail field through log message properties.
• Newest Elmah.Io.Client.
• Made an OnInstallation hook available in options.

We released a new version (5.3.52) of the Elmah.Io.Client.Extensions.SourceCode package. The new version includes the following changes:

• Newest Elmah.Io.Client.
• Upgraded build image to Windows 2025.

We released a new version (5.3.18) of the Elmah.Io.Client.Extensions.Correlation package. The new version includes the following changes:

• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.

We released a new version (5.3.131) of the Elmah.Io.Client package. The new version includes the following changes:

• Built with the newest version of NSwag, which contains several code improvements (code is still backwards-compatible).
• Added OnInstallation event plus extended CreateInstallation with a list of environment variables. Environment variables will be fully available in the upcoming Elmah.Io.Client v6.
• Added missing JSON settings for SourceMapsClient.
• Added EnvironmentVariablesHelper. This is primarily used within the Elmah.Io.* client integrations.
• Upgraded build image to Windows 2025.

Unless security issues are identified, this will be the last version of Elmah.Io.Client v5. The upcoming v6 will contain several improvements and run on a new major version of the elmah.io API.

We released a new version (5.3.88) of the Elmah.Io.AspNetCore package. The new version includes the following changes:

• Made an OnInstallation hook available in options.
• Newest Elmah.Io.Client.

We released a new version (5.3.60) of the Elmah.Io, Elmah.Io.AspNet, Elmah.Io.Mvc, and Elmah.Io.WebApi packages. The new version includes the following changes:

• Newest Elmah.Io.Client.
• General code improvements by fixing all code suggestions.
• Upgraded build image to Windows 2025.

A new bulk action is now available that hides all messages in a search result. While adding this, we also renamed the existing actions to make it clearer that actions are done on the current search result.

https://blog.elmah.io/expression-trees-in-c-building-dynamic-linq-queries-at-runtime/

Learn how to use C# expression trees to build dynamic LINQ queries at runtime with practical examples, use cases, and performance tips.