Version 2.1.11

Version 2.1.11 - 26.09.2024

Bugfix:

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

Version 2.1.10

Version 2.1.10 - 02.07.2024

Improvements:

• Updated dependencies to the latest version.
• On uncaught exception, store a report in the database rather than 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

Backtrace 2.1.8

Version 2.1.8 - 26.03.2020

• Fixed self referenced object serialization errors.

Backtrace C# library 2.1.3

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

Backtrace C# library 2.1.1

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

Backtrace C# library 2.1.0

Version 2.1.0 - 12.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.

Backtrace C# library 2.0.7

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.

Backtrace C# library 2.0.6

Version 2.0.6 - 20.12.2018

• New BacktraceCredentials constructor,
• UnhandledThreadException flow

Backtrace C# library 2.0.5

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

Backtrace C# library 2.0.4

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,