-
Notifications
You must be signed in to change notification settings - Fork 245
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
Is this suitable for use with Blazor? #315
Comments
Hello, The problem does not come from the library, but the way EntityFramework works with Blazor. Maybe, this PR #289 will introduce a new way to work with. |
I recommend my clients avoid Blazor Server because of the EF lifetime issues it has. Blazor WebAssembly avoids all such issues by working with APIs, and EF (and Specifications) work great in APIs. |
While I do agree with the API first approach, the PR #289 looks quite useful and worth looking into. |
Closing the issue, the feature is published in version 7. |
I understand its better to use a context factory with Blazor to avoid scope issues. I currently use it and get "a second operation was started on this context.." warnings
The text was updated successfully, but these errors were encountered: