-
-
Notifications
You must be signed in to change notification settings - Fork 6
MethodAccessException thrown when AddEntityFramework is called #4
Comments
Which version of the As we can see on NuGet.org: The latest version of |
Yes, I'm using version 1.0.0 of the Sentry package. The dependency is marked as ">=" so I was just following that. Looking forward to the updated package. Do you have an ETA? Perhaps the dependency should be corrected if the update isn't imminent. |
@mungk This is not a high priority ATM but we'd be happy to merge a PR. All it's needed is updating ,in this repository, the dependency After that I can publish the package. |
@bruno-garcia Unfortunately, upgrading the
Choice 1 seems reasonable to me, but I don't claim to know the Choice 2 seems like a burden moving forward as more and more extensions are added because they'll each need to be included on the list. Either way, it's a change to the |
You are right. I'm leaning towards making them public again although that is not part of the unified API of the Sentry SDKs. If you'd like to PR making those methods again public, I'd be happy to merge it in. |
@mungk We still need to release a new version of Until then you could try setting /cc @xt0rted |
The only build error I'm seeing right now is due to |
Here is a temporary fix til
Also, make sure to change the namespace of the file to Sentry.EntityFramework to avoid namespace collisions (or change the class name from This works fine (performance doesn't matter since it's normally only called at startup) but I don't want to commit this into the repo cause it's ugly as hell. |
@xt0rted's fix is published to NuGet as a preview package along with a few more changes. |
Version 1.0.0 was released. |
I'm following the example pretty closely. My code looks like this:
However, when the AddEntityFramework method is actually executed as the site is initializing, it throws the following exception:
Visual Studio doesn't detect any issues in the editor or when it's compiled. It only occurs on execution. My only thought is that the SentryOptionsExtensions.AddExceptionProcessor is defined as internal and that is preventing the call from being successful at runtime.
Thoughts?
Thanks!
Andy
The text was updated successfully, but these errors were encountered: