ExceptionReporter 2.2.0
See the version list below for details.
dotnet add package ExceptionReporter --version 2.2.0
NuGet\Install-Package ExceptionReporter -Version 2.2.0
<PackageReference Include="ExceptionReporter" Version="2.2.0" />
paket add ExceptionReporter --version 2.2.0
#r "nuget: ExceptionReporter, 2.2.0"
// Install ExceptionReporter as a Cake Addin #addin nuget:?package=ExceptionReporter&version=2.2.0 // Install ExceptionReporter as a Cake Tool #tool nuget:?package=ExceptionReporter&version=2.2.0
ExceptionReporter is a .NET component that shows a dialog with detailed information on an Exception and the application/system running it. It allows the application user to copy, save and/or email a report of the incident - including a screenshot
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net40-client is compatible. |
-
.NETFramework 4.0 Client
- DotNetZip (>= 1.10.1)
- Simple-MAPI.NET (>= 1.0.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on ExceptionReporter:
Repository | Stars |
---|---|
jwallet/spy-spotify
🎤 Records Spotify to mp3 without ads and adds media tags to the files 🎵
|
New Feature:
Automatically compress all files that are specified for attachment into a single zip file (excluding files already with .zip extension)
Fixes/Changes:
Fix SMTP support including adding SSL/credentials and to be properly configurable via code. Also added specific SMTP error display for diagnosis
Removed XML config in favor of code config. The "Config" tab is also therefore removed. The idea here would be that you'll either hardcode some values and/or derive some from your own App config.
Internal/structural:
Removed embedded Win32Mapi library and switched to using a nuget dependency to include support for Simple-MAPI.NET ie for using embedded email client for emails
The base .NET runtime is 4.0 Client
The assembly is no longer signed - if I could figure out a way to provide signed/unsigned I would do it - let me know if being unsigned is a hassle
Removed the WPF infrastructure - the code that used reflection to determine whether the assembly was WPF/Winforms was of no use since the WPF version did not get worked on. There will be some kind of performance boost from removing this