Skip to content

Latest commit

 

History

History
182 lines (113 loc) · 7.79 KB

CHANGELOG.md

File metadata and controls

182 lines (113 loc) · 7.79 KB

Backtrace C# Release Notes

Version 2.1.11 - 26.09.2024

Bugfix:

  • Fixed an Exception due to unsupported process.TotalProcessorTime usage (#44).

Version 2.1.10 - 02.07.2024

Improvements:

  • Updated dependencies to the latest verison.
  • On uncaught exception, store a report in the database rather sending it to API. If the database is not available, try sending a report to the server (#36).
  • Added application.session, application.version, backtrace.agent and backtrace.version attributes.
  • Read application.version and version attributes only when the assembly is available.
  • Added support for the error.type attribute (#42).
  • Fixed the problem when the guid attribute value was set incorrectly (#43).

Maintenance:

  • Removed codeql-analysis action
  • Moved testing and building to Github action (#37, #40)
  • Added a CICD pipeline for releasing a new version of libraries

Version 2.1.9 - 08.06.2019

  • Changed acces modifiers in BacktraceData object. With this change, BeforeSend event allows to change Annotations, ThreadInformation and SourceCode property

Version 2.1.8 - 26.03.2020

  • Fixed self referenced object serialization errors.

Version 2.1.7 - 02.03.2020

  • Fixed nullable attributes -
  • Fixed analysing assembly data: EXE is not a .NET EXE - (#29)

Version 2.1.6 - 11.10.2019

  • Changed AppDomain exception handler - now Backtrace library will try to store report in database instead of sending report to Backtrace. Because of that we won't block application on unhandled exception event handler.

Version 2.1.5 - 04.10.2019

  • Changed AppDomain exception handler - now Backtrace library will try to send report synchronously instead of using async API.

Version 2.1.4 - 02.08.2019

  • BacktraceDatabase additional null check in LoadReports method.

Version 2.1.3 - 13.06.2019

  • Fixed a problem with missing path to attachments when Backtrace C# client read report from hard drive,
  • Fixed a problem with missing minidump files in report attachments

Version 2.1.2 - 07.06.2019

  • BacktraceData now allows to edit attachments in BeforeSend event.

Version 2.1.1 - 18.03.2019

  • BacktraceCredentials allows you to pass WebProxy object to Proxy property. BacktraceApi will use proxy object to create HttpClient

Version 2.1.0 - 10.03.2019

  • Deduplication parameters. Now BacktraceDatabaseSettings allow you to setup deduplication rules. If you use deduplication types, you can aggregate existing reports and send only one message for all the same reports.
  • BacktraceDatabase allows you to override default deduplication methods and generate your own hash per diagnostic data,
  • BacktraceResult now allows you to retrieve exception object if BaktraceResult has status ServerError,
  • When Backtrace library send diagnostic data to server any exception happend, library will print information about error by using Trace interface.

Version 2.0.7 - 11.02.2019

  • If you send exception, BacktraceReport will generate stack trace based on exception stack trace. We will no longer include environment stack trace in exception reports,
  • Unit tests fix - incrementation fix,
  • BacktraceDatabase fix for FirstOrDefault invalid read.

Version 2.0.6 - 20.12.2018

  • New BacktraceCredentials constructor,
  • UnhandledThreadException flow

Version 2.0.5 - 03.12.2018

  • Removed unused usings,
  • BacktraceDatabase conditions with maximum number of records/maximum disk space fix,
  • Removed invalid tests from Backtrace.Tests solution.

Version 2.0.4 - 23.09.2018

  • BacktraceClient allows developer to unpack AggregateException and send only exceptions available in InnerExceptions property.
  • BacktraceReport accepts two new properties: Factor and Fingerprint. These properties allows you to change server side algorithms.
  • BacktraceData now include informations about Exception properties. You can check detailed Exception properties in Annotations.
  • BacktraceDatabase doesn't throw exception when developer can't add new record. This situation exists when database was full or database hasn't enough disk space for exceptions.
  • BacktraceResult can use new Status. In case when developer want to unpack AggregateException and InnerExceptions property is empty, BacktraceClient return BacktraceResult with status Empty,

Version 2.0.3 - 04.09.2018

  • Thread data condition for Unity on .NET Framework 4.5+

Version 2.0.2 - 28.08.2018

  • Nullable environment variables fix,
  • Fix for invalid database tests that use real minidump files,
  • Fix nullable GetEnvironmentValue results.

Version 2.0.1 - 17.07.2018

  • BacktraceClient use reflection to generate better method names for async state machine stack frames,
  • BacktraceReport allows to disable reflection feature by using additional constructor parameter,
  • BacktraceClient use BacktraceStackTrace and BacktraceStackFrame instead of DiagnosticStack.

Version 2.0.0 - 10.07.2018

  • BacktraceDatabase use BacktraceRecord instead of BacktraceEntry,
  • BacktraceDatabase new parameters - size limit and maximum number of record in database,
  • New information about current assembly in BacktraceReport attributes,
  • New directory for sample Backtrace projects,
  • BacktraceReport don't use anymore BacktraceReportBase. All BacktraceClient and BacktraceDatabase events use BacktraceReport instead of BacktraceReportBase.

Version 1.3.2 - 03.07.2018

  • Fixed a invalid type for process.age attribute

Version 1.3.1 - 28.06.2018

  • Fixed a double-dispose bug in BacktraceApi

Version 1.3 - 26.06.2018

  • Attributes dictionary now use an object type instead of a generic type for better flexibility,
  • OnClientReportLimitReached use BacktraceReportBase instead of BacktraceReport,
  • BacktraceResult store BacktraceReportBase instead of BacktraceReport.

Version 1.2.3 - 21.06.2018

  • Enum is now available as a primitive value in BacktraceAttributes.

Version 1.2.2 - 19.06.2018

  • Ignore exception object in BacktraceReport in serialization. Change exception conditions in BacktraceReport.

Version 1.2.1 - 14.06.2018

  • Invalid serialization support.

Version 1.2.0 - 09.05.2018

  • BacktraceDatabase - offline error report storage and auto re-submission support in the event of network outage and server unavailability,
  • BacktraceClient.Send now works properly with TLS 1.2 under .NET 4.6+ and .NET Core 2.0. However, BacktraceClient.SendAsync is strongly recommended whenever possible,
  • Removed TlsLegacySupport flag in BacktraceClient.

Version 1.1.4 - 27.04.2018

  • Fix: A bug where casing of some fields is changed after JSON serialization.

Version 1.1.3 - 13.04.2018

  • Improved async Task sample applications.

Version 1.1.2 - 09.04.2018

  • Fix: Clean Backtrace client’s data storage on startup.

Version 1.1.1 - 09.04.2018

  • Error reports now include debug attributes,
  • BacktraceClient.OnClientReportLimitReached event handlers will now take BacktraceReport as a parameter,
  • Refactoring of JSON Data code,
  • .NET 4.5 example with async task usage,
  • Better stack trace analysis,
  • Fix: Reporting unhandled application exceptions now uses SendAsync and proper TLS 1.2 support.

Version 1.1.0 - 30.03.2018

  • BacktraceClient now supports an asynchronously SendAsync method that works with async task,
  • For .NET Framework 4.5 and .NET Standard 2.0, BacktraceClient now streams file attachment content directly from disk via SendAsync method,
  • AfterSend event parameter changed. Now AfterSend event require BacktraceResult parameter, not BacktraceReport,
  • Send and SendAsync method now returns BacktraceResult with information about report state,
  • OnServerResponse now require BacktraceResult as a parameter.

Version 1.0.0 - 19.03.2018

  • First release.