Starts in:
1 DAY
2 HRS
19 MIN
8 SEC
Starts in:
1 D
2 H
19 M
8 S
Open Closed

AsyncExecuter Error #582


User avatar
0
ishaq.alzidi created

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

  • ABP Framework version: v3.3.1
  • UI type: Angular
  • ** Identity Server Seperated (Angular)**:
  • Exception message and stack trace:
  • Cannot access a disposed object. A common cause of this error is disposing a context that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling Dispose() on the context, or wrapping the context in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances
  • Steps to reproduce the issue: Run Test

I'm getting an error while I'm running AsyncExecuter with any methods (FirstOrDefaultAsync, ToListAsync ... etc) in test projects or in scope dependency injection the exception message is

Cannot access a disposed object. A common cause of this error is disposing a context that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling Dispose() on the context, or wrapping the context in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances

1 Answer(s)
  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    Can you provide some code?

Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06