Version 2.1.7: Fixed Backtrace Attributes null checks

Backtrace/Backtrace.csproj

@@ -4,7 +4,7 @@
     <TargetFrameworks>netstandard2.0;net45;net35</TargetFrameworks>
     <PackageRequireLicenseAcceptance>true</PackageRequireLicenseAcceptance>
     <PackageTags>Backtrace Error Diagnostic Tools Debug Bug Bugs StackTrace</PackageTags>
-    <PackageVersion>2.1.6</PackageVersion>
+    <PackageVersion>7</PackageVersion>
     <Product>Backtrace</Product>
     <PackageLicenseUrl>https://github.com/backtrace-labs/backtrace-csharp/blob/master/LICENSE</PackageLicenseUrl>
     <PackageProjectUrl>https://github.com/backtrace-labs/backtrace-csharp</PackageProjectUrl>
@@ -13,13 +13,13 @@
     <Summary>Backtrace's integration with C# app allows customers to catch and report handled and unhandled C# exceptions to their Backtrace instance, instantly offering the ability to prioritize and debug errors.</Summary>
     <RepositoryUrl>https://github.com/backtrace-labs/backtrace-csharp</RepositoryUrl>
     <NeutralLanguage>en</NeutralLanguage>
-    <Version>2.1.6</Version>
+    <Version>2.1.7</Version>
     <PackageLanguage>en-US</PackageLanguage>
     <Copyright>Backtrace I/O</Copyright>
     <Authors>Backtrace I/O</Authors>
     <Company>Backtrace I/O</Company>
-    <AssemblyVersion>2.1.6.0</AssemblyVersion>
-    <FileVersion>2.1.6.0</FileVersion>
+    <AssemblyVersion>2.1.7.0</AssemblyVersion>
+    <FileVersion>2.1.7.0</FileVersion>
   </PropertyGroup>
 
   <ItemGroup>

Backtrace/Model/JsonData/BacktraceAttributes.cs

@@ -101,6 +101,7 @@ private void SetDebuggerAttributes(Assembly callingAssembly)
                 Attributes["build.debug"] = false;
                 Attributes["build.jit"] = true;
                 Attributes["build.type"] = "Release";
+                return;
             }
             // Just because the 'DebuggableAttribute' is found doesn't necessarily mean
             // it's a DEBUG build; we have to check the JIT Optimization flag
@@ -130,6 +131,11 @@ private void ConvertAttributes(BacktraceReport report, Dictionary<string, object
             var attributes = BacktraceReport.ConcatAttributes(report, clientAttributes);
             foreach (var attribute in attributes)
             {
+                if (attribute.Value == null)
+                {
+                    continue;
+                }
+
                 var type = attribute.Value.GetType();
                 if (type.IsPrimitive || type == typeof(string) || type.IsEnum)
                 {

CHANGELOG.md

@@ -1,22 +1,33 @@
 # Backtrace C# Release Notes
 
+## Version 2.1.7 - 02.03.2020
+
+- Fixed nullable attributes -
+- Fixed analysing assembly data: EXE is not a .NET EXE - (https://github.com/backtrace-labs/backtrace-csharp/issues/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. 
+
+- `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
@@ -27,11 +38,13 @@
 - 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