Skip to content

Releases: MindscapeHQ/raygun4net

Support FtpWebResponse

09 Jul 07:10
Compare
Choose a tag to compare
  • The RaygunMessageBuilder now recognises FtpWebResponse and will extract the status code. This resolves an invalid cast exception. Other types of WebResponse will also be handled nicely.

Version 3.0

26 Jun 05:13
Compare
Choose a tag to compare
  • ignoreFormDataNames has been removed and replaced with 4 separate options: ignoreFormFieldNames, ignoreHeaderNames, ignoreCookieNames and ignoreServerVariableNames.
  • Setting one of these new options to * will prevent any value from that category from being sent to Raygun.io.
  • Placing * before, after or at both ends of an ignored key will be used as an ends-with, starts-with or contains condition respectively.
  • The RaygunClient methods that accepted IEnumerables have been changed to be multi-parameter methods.
  • Added RaygunClient.UserInfo property, and RaygunIdentifierMessage.IsAnonymous property.
  • All obsolete members from the previous version have been removed.

Avoid sending duplicate exceptions

17 Jun 04:40
Compare
Choose a tag to compare
  • This release fixes a bug in the previous release where some exceptions were not being logged in an MVC application when using the Raygun http module.
  • To get the above fix working, Raygun4Net will now mark exceptions as already-sent to avoid sending the same message multiple times.
  • Resolved a potential Null ReferenceException in Raygun4Net.WinRT

Improved MVC support

04 Jun 02:46
Compare
Choose a tag to compare
  • Raygun can now send exceptions in an MVC application that is using a HandleErrorAttribute to suppress page crashes.
  • Resolved a duplicate key exception when creating the cookies list to send.
  • Added RaygunClient.ProxyCredentials property.

Modify or cancel sent messages

30 May 04:54
Compare
Choose a tag to compare
  • Added RaygunClient.SendingMessage event to the main .Net provider. This can be used to make final modifications to the message, or to cancel the send operation.
  • Added IRaygunApplication which can be used to provide a custom RaygunClient to the HttpModule.
  • If a windows phone is connected to the internet, but fails to send a message, it will be saved to the device to send later.

.Net2.0 support

22 May 23:18
Compare
Choose a tag to compare
  • Raygun4Net now supports projects targeting .Net2.0 (both web and desktop apps). This is available in both the standard and signed NuGet pacakges.

Standard: https://www.nuget.org/packages/Mindscape.Raygun4Net

Signed: https://www.nuget.org/packages/Mindscape.Raygun4Net.Signed

Filter ignored cookies and optionally disable Raygun on local host

16 May 03:13
Compare
Choose a tag to compare
  • The IgnoredFormNames feature will now filter out cookies which now have their own section in the request data.
  • When enabling Raygun4Net via the http module, the new excludeErrorsFromLocal option on RaygunSettings can be set to true to prevent any exceptions being logged from your debug/dev environment.
  • Corrected the window width/height values in the Raygun4Net provider.

Improved Xamarin.Android stack traces

30 Apr 03:14
Compare
Choose a tag to compare
  • Improved stack traces for Xamarin.Android errors that occur in async methods.
  • Removed unused Android permission: access external storage.
  • Can now specify IgnoreFormDataNames in config file.
  • Provided a signed version of the .NET and WinRT Raygun providers: https://www.nuget.org/packages/Mindscape.Raygun4Net.Signed/2.0.4

Removed Bluetooth requirement for Android.

24 Mar 02:55
Compare
Choose a tag to compare
  • Removed Bluetooth permission requirement from Xamarin.Android provider.

Code clean + some improvements

03 Feb 01:53
Compare
Choose a tag to compare
  • Cleaned the code of all .Net providers. Removed preprocessor directives, unused and obsolete code.
  • Added RaygunClient.ApplicationVersion property to conveniently replace Send method overloads.
  • Added RaygunClient.Attach method for WinRT and Windows Phone to simplify set up.
  • Improved stack trace information for WinRT and Window Phone.
  • Windows Phone provider now includes device manufacturer, hardware and firmware versions, screen dimensions, available isolated storage memory, and application usage memory values in error reports.
  • WinRT provider now includes screen dimensions and application state (full screen, filled, snapped etc) values in error reports.