Heads up! – Raygun4Net 4.0 coming soon

Jason FauchelleProvider Updates5 Comments

Very soon we will be releasing version 4.0 of the Raygun4Net provider! If you are using Raygun in an MVC or WebApi project, then there is an important change that you need to be aware of: MVC and WebApi support is being moved into their own NuGet packages. This is to resolve some referencing issues that a few customers have come across.

What does this mean for you?

If you are using Raygun in an MVC or WebApi project, please uninstall the existing Raygun4Net package, and then install the Raygun4Net.Mvc or Raygun4Net.WebApi package as appropriate. These NuGet packages are available right now. Once you’ve installed the new package, you’ll be able to use Raygun4Net in the exact same way as before.

Raygun4Net NuGet Packages

The MVC and WebAPI packages also include all the features of the existing Raygun4Net package such being able to manually send errors. The MVC and WebApi packages can even be installed into the same project if you need support for both of these.

Release date for V4 of the Raygun4Net package

Version 4.0 of the standard Raygun4Net NuGet package will be released on Monday the 27th of October. This is to give MVC and WebApi devs a chance to switch to the new packages before the MVC and WebApi support is no longer part of the standard Raygun4Net package. The standard Raygun4Net package is what you want for non-MVC or non-WebApi projects such as WPF, ASP .NET, Windows Phone, Windows Store, WinRT and Xamarin.

If you have any questions, don’t hesitate to ask in the comments below.

Looking for an error reporting solution for all your .Net projects? Sign up for a free trial of Raygun now – no credit card required.

Next level software intelligence across your entire stack.

5 Comments on “Heads up! – Raygun4Net 4.0 coming soon”

  1. Stefan Kip


    In some projects we’re using WebAPI, but I’m not sure if we’ve done anything special to report exceptions in WebAPI.
    How can we find out whether or not we need to include the WebAPI part as well?

    Ps; this has been done to fix depencies with System.Web.Http, hasn’t it? I’ve seen the error a couple of times and fixed it by installing the Microsoft.AspNet.WebApi NuGet package, which I really didn’t need at all.

    Cheers, Stefan.

  2. Jarle Nygård

    Question; what if we have mixed projects… So we have an Azure Worker Role that exposes a OWIN Web API endpoint… We’re currently just using the Raygun4Net package and not API specific setup at all.

  3. Jason Fauchelle

    Hi Stefan,

    You can see what Raygun does when attaching to a WebApi project here: https://github.com/MindscapeHQ/raygun4net/blob/master/Mindscape.Raygun4Net.WebApi/RaygunWebApiClient.cs#L76

    To make sure you don’t miss out on any exceptions, it is best to use the Raygun4Net.WebApi package in your WebApi projects.

    Note that this package can not currently be used side-by-side with the standard Raygun4Net package. It does however have all the features that the standard package has such as manually sending exceptions or attaching custom data. Also, the Raygun4Net.Mvc package can be used side-by-side with the WebApi package which will include the http module and of course MVC support.

    And yes you are correct that this has been done to resolve dependency issues such as System.Web.Http as you pointed out.

    Please let me know if you have further questions about this.

    -Jason Fauchelle

  4. Jason Fauchelle

    Hi Jarle,

    If you weren’t using any Web API specific setup, then you should be able to continue using the standard Raygun4Net package and continue using it in the same way as you are now. Version 4 of the standard Raygun4Net provider has been released, so you can try that out now. If you run into any trouble or have further questions, please let me know.

    -Jason Fauchelle

Leave a Reply

Your email address will not be published. Required fields are marked *