Migrating to .Net Core

Mike

Posted on
Feb 25 2017

I have an app that was migrated over to .net core, basically a total rewrite. I've followed the set up instructions for raygun on the .net core and are using the same api key that was used for the older app. However, no errors seem to be logged. I'm wondering if it is necessary to create a new Application with a new api key. Any advice?

John-Daniel Trask

Raygun

Posted on
Feb 25 2017

Hi Mike,

It shouldn't require a new app, no. I'll loop in one of our engineers who worked on the .NET Core Provider. My first thought is more that it'll be a version compatibility issue (we're using .NET Core at Raygun for some new sub-systems, and while it's been evolving, the version story is a bit of a challenge to deal with. Could be wrong that this is part of the issue -- I'll leave it with the expert!).

In the meantime, could you share:

  1. What version of .NET Core you're using
  2. How you've integrated Raygun
  3. Any other frameworks you're using

Thanks!

John-Daniel Trask

Reply