NetStandard 2.0 support?

[DamienDennehy]

As NetStandard 2.0 is compatible with .NET Framework 4.6.1, it looks like something that Raygun could support. It is on the product roadmap in the nearby future?

I know that Mindscape.Raygun4Net.AspNetCore supports NetStandard 1.4, but moving this support into the main Raygun NuGet would be a huge advantage.

My team's goal is use the same Raygun NuGet package across our Android, Desktop and Web APIs.

[CmdrKeen]

Hi Damien,

Unfortunately our main .NET library for Raygun is designed to support back to .NET 2.0 so it's not likely we'll move that requirement to .NET 4.6.1 / NetStandard2 in the very near term.

I'll chat more with the team but I suspect it might be smarter to simply evolved the Core provider to be more of a NetStandard provider, and keep it at feature parity.

[DamienDennehy]

Hi John,

Ah got it, understand the issue with .NET 2.0. Using the Core provider for NetStandard sounds great!

We would be happy to migrate from Mindscape.Raygun4Net.AspNetCore to Mindscape.Raygun4Net.Core as this would allow us to drop AspNetCore from our libraries.

[alastairs]

As far as I can see the Core library only defines the message types and doesn't provide much functionality. I'm currently looking at Raygun for .NET Core 2.0 command-line apps (back-end services) and would really appreciate a .NET Standard 2.0 implementation.

How feasible would it be to, e.g. provide two NuGet packages, one that supports .NET Standard 2.0 (and thus .NET 4.6.1+), and one that supports the older .NET 2.0-3.5.2 frameworks?

[SergeBerwert]

Need .Net Standard 2.0 support too. We also us the Mindscape.Raygun4Net usually.

[j5alive]

The current Raygun4Net.AspNetCore library does work with Net Standard 2.0, however it does reference all the MVC libraries so is probably not something you want to use? We'll be looking into this soon, but I can't say exactly when we'll have the libraries updated sorry.

[robertmiles3]

It's been 3 months...got an update?

[rogihee]

Please create a seperate NuGet with .Net Standard support, we need this as well

[anfomin]

Raygun4Net lacks .NET Core 2.0 support so I've created custom library RaygunCore for every one.

[robertmiles3]

@CmdrKeen Any update? With respect, it seems odd to hamstring newer stuff with the idea of supporting all the way back to .NET 2.0 given that even 4.5.1 was EOL'd over 2 years ago.

[CmdrKeen]

@robertmiles3 I’ve had the team bump the priority around building out a NetStandard2 provider. Should be started this week.

[mduncan26]

@robertmiles3 We have released a new provider for NetStandard2. It can be found here on NuGet: https://www.nuget.org/packages/Mindscape.Raygun4Net.NetCore/ and the source is located in our Raygun4Net repository here: https://github.com/MindscapeHQ/raygun4net/tree/master/Mindscape.Raygun4Net.NetCore.

[bartdkmediahuis]

Is this ticket still "open" because it's in preview state ? Or can this be used in production ?

[mduncan26]

@bartdkmediahuis Apologies it can be used in production. I will close this issue.

[DamienDennehy]

This is really excellent to hear. Thank you for the support!

[robertmiles3]

Thanks @CmdrKeen and @mduncan26!

[ZhengRaygun]

Hi everyone, we've now also published a blog post on our recent support for .NET Standard 2.0 and ASP.NET Core 2. You can read the details here: https://raygun.com/blog/net_core_2-0_support/

Thank you for your request!