elmah.io changelog

We are currently testing a new version of app.elmah.io running on ASP.NET Core. If everything goes well, we will release it next week (March 9 and forward). Nothing visible is expected to change, but we have switched to the new authentication system available in ASP.NET Core. This means that you will need to log in again no matter if you have the Stay signed in toggle enabled or not. We are sorry for the inconvenience caused by this but we look forward to continuing our journey of improving the app.

We released a new version (3.3.36) of the Elmah.Io.Functions package. Here are the included changes:

• XML documentation.
• Newest Elmah.Io.Client.

A quick comment about the obsolete warning showed when using the package. Microsoft marked IFunctionFilter as obsolete. Not because it will be removed, but because they may change the way attributes work in functions in the future. For now, you can suppress this warning with the following code:

#pragma warning disable CS0618 // Type or member is obsolete
builder.Services.AddSingleton<IFunctionFilter, ElmahIoExceptionFilter>();
#pragma warning restore CS0618 // Type or member is obsolete

We released a new minor version of the Elmah.Io.AspNetCore package. The new version includes XML documentation for all methods. This goes for both error logging and heartbeats (ASP.NET Core Health Checks).

We released a new minor version of the Elmah.Io.Client package. The new version includes XML documentation for all methods. Unless you are developing directly against the client, there is no need to update. If you are on an older version than 3.7.79, now could be a good time to update 👍

There’s a new discount in the elmah.io Goodiebag: 10% off on AspNet Zero. AspNet Zero is a Visual Studio solution for building web applications with a modern UI and SOLID architecture.

https://blog.elmah.io/generate-a-pdf-from-asp-net-core-for-free/

We re-wrote the New Error email template in MJML, making it look better across email clients. We also introduced a new monospaced font for the details section, resulting in beautiful looking stack traces even in your email client.

https://blog.elmah.io/asp-net-core-middleware-with-roslyn-analyzers-part-1/

https://blog.elmah.io/how-to-send-emails-from-csharp-net-the-definitive-tutorial/

The final part of the app revamp has been deployed. The updated log search page has been rebuilt to look better than ever:

All of the tabs have been visually improved, like the Uptime tab:

This change also introduces a beautiful new look and feel for Heartbeats:

Let us know what you think.

There’s a new version of the Elmah.Io.AspNetCore.HealthChecks package. We made the report published by ASP.NET Core better by grouping by severity:

We just published a new issue of the elmah.io Newsletter: https://mailchi.mp/c75f854345ca/stable-api-uptime-monitoring-included-and-a-present-2687495

If you want to receive an email every 2-3 months with all of the recent goodies on elmah.io, make sure to subscribe here: http://eepurl.com/dE1hCn

https://blog.elmah.io/csharp-how-to-convert-a-string-to-int/

https://blog.elmah.io/publish-a-self-contained-net-core-app-on-azure-devops/

You may remember back in August and September of last year when we introduced structured logging and started grouping messages by the new message template field. Today, we released the third (and final so far) step in getting structured logging to elmah.io. With today’s change, we now calculate the isNew flag based on the messageTemplate field rather than looking at message. In short, this means that we will now only set isNew to true on one of the following log messages (previously, both were set to new):

log.Information("Error while saving {UserId}", 1);
log.Information("Error while saving {UserId}", 2);

The isNew algorithm still looks at a range of different fields (like URL and source of the error). If the message above is logged from two different URLs, both messages will be marked as new to help you identify that the error happened on multiple pages.

We fixed an issue that would cause some apps not to work after a re-install. If you experience elmah.io apps that don’t work, please try to re-install the app. If still not working, don’t hesitate to reach out to our support.

Those of you who use the integration between Azure DevOps and elmah.io may have noticed the following warning in the log when notifying elmah.io about a new release:

##[warning]Task 'ElmahIoDeploymentNotification' (3.1.1) is using deprecated task execution handler. The task should use the supported task-lib: https://aka.ms/tasklib

We released a new version which fixes this warning. The new integration is automatically rolled out to your pipelines. If you experience any problems in this process, it can be installed manually from here: https://marketplace.visualstudio.com/items?itemName=elmahio.deploy-tasks

We released a new version (3.8.99) of the Elmah.Io.AspNetCore package. The biggest change is support for elmah.io Heartbeats. We are not quite ready to move Heartbeats out of beta yet, but the new package for ASP.NET Core is production-ready. Here are the included new features and bugfixes:

• Support elmah.io Heartbeats through ASP.NET Core Health Checks.
• New sample for ASP.NET Core 3.x.
• Newest Elmah.Io.Client.
• Increased timeout in MessageShipper since code is executed behind a queue.
• Fixed a bug when posting form data without a content type.
• Upgraded tag helper to include elmah.io.javascript version 3.1.1.

We released a new version (3.6.82) of the Elmah.Io.NLog package. Here are the included new features and bugfixes:

• Target netstandard2.0 to reduce dependencies for newer .NET and .NET Core apps.
• Use NLog’s ${environment-user} to fill the user field.
• Newest Elmah.Io.Client.
• Forward errors during communication with the elmah.io API to NLog’s InternalLogger.
• Increased timeout unless explicit set through TaskTimeoutSeconds.
• Fixed a bug that would cause web-related errors in the internal log when using the package from a console app.

https://blog.elmah.io/paid-subscriptions-with-asp-net-core-and-stripe-billing/