-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrations: Entity Framework Core #161
Comments
I'm working with the EF team on best approaches here: dotnet/efcore#7939 |
Closing this out, a new package is available for testing: MiniProfiler.EntityFrameworkCore. I welcome issues anyone hits and it'll continue to progress as |
Works great. And "just works" with ASP.NET Identity (specifically Microsoft.AspNetCore.Identity.EntityFrameworkCore) which was always problematic with MVC in the past. Inside Startup.Configure I had some database access. Initialization isn't fully complete yet (I believe MiniProfiler.Current isn't set) and it throws an exception in RelationalDiagnosticListener.cs/OnBeforeExecuteCommand. Moving the database calls above app.UseMiniProfiler(...) is a workaround. |
@chadwackerman Doh, I'm stupid...not sure why I made that throw. Next build will include adbdca2 to fix that bad behavior. |
I believe I'm seeing a variation of this on alpha8-165. Program.cs:
If I remove .AddEntityFramework() from the services.AddMiniProfiler() call in Startup.cs, it works. |
What error does it throw? |
|
Fixed on alpha9-202 |
Closing this out to clean up :) |
Originating in #130, need to see how Entity Framework Core works, likely create
MiniProfiler.EntityFrameworkCore
(orMiniProfiler.Providers.EntityFrameworkCore
, depending on the integration) and get a sample in.MiniProfiler.Providers.EntityFrameworkCore
packageThe text was updated successfully, but these errors were encountered: