Starts in:
2 DAYS
1 HR
7 MIN
20 SEC
Starts in:
2 D
1 H
7 M
20 S

Activities of "Josh"

Hey Maliming,

Yeah, weird it just occurs randomly from refreshing for us, so apart from saying just refresh some more which isn't very helpful, do you have Discord or Microsoft Teams which would allow us to hop into a call and try reproduce the issue together giving you a better idea of the issue since you are having issues reproducing it yourself?

Regards, Josh.

Hey Maliming,

I don't believe it's possible for me to directly share them with you nor legal for me to, but you can simply signup for the free trial at https://nuget.devexpress.com/, which gives you access to the relevant packages. You can also download other parts of the DevExpress Trial such as the Report Explorer at https://go.devexpress.com/DevexpressDownload_UniversalTrial.aspx.

Other information on obtaining and using the trial NuGet Feed can be found at the following: Obtaining Trail Nuget Feed: https://docs.devexpress.com/GeneralInformation/120534/installation/install-devexpress-controls-using-nuget-packages/net-core-controls-via-nuget Setup VS Studio Nuget Package Manager: https://docs.devexpress.com/GeneralInformation/116698/installation/install-devexpress-controls-using-nuget-packages/setup-visual-studios-nuget-package-manager

If you need any more help in getting those packages let me know and I'm happy to assist further. And thank you again for the help with this issue, I appreciate it.

Thanks, Josh.

Thank you.

Appreciate you looking into this.

Hey maliming,

I have sent through a few emails with the project source code as per requested, feel free to take a look and either respond here or via email. Thanks for the help in advance.

Regards, Josh.

  • ABP Framework version: v7.0.0
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes / no
  • Exception message and stack trace: ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance 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 instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. ObjectDisposed_ObjectName_Name
  • Steps to reproduce the issue:
  • Followed steps as shown here along with a few changes to get it to actually work at all: [Scoped Db Context #1265](https://support.abp.io/QA/Questions/1265), [Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed. #1698](https://support.abp.io/QA/Questions/1698/Instances-cannot-be-resolved-and-nested-lifetimes-cannot-be-created-from-this-LifetimeScope-as-it-or-one-of-its-parent-scopes-has-already-been-disposed)
  • Issue occurs randomly when using the Report Viewer, along with memory constantly increasing every time a report is viewed.
  • I have made a github repo with the relevant code from a fresh project so feel free to lookover that and give me some suggestions, thanks. Github
Showing 11 to 15 of 15 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06