Devexpress.xtraprinting Nuget

[Mertie Oldow]

Idon'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 , which gives you access to the relevant packages. You can also download other parts of the DevExpress Trial such as the Report Explorer at _UniversalTrial.aspx.

Other information on obtaining and using the trial NuGet Feed can be found at the following:Obtaining Trail Nuget Feed: -devexpress-controls-using-nuget-packages/net-core-controls-via-nugetSetup VS Studio Nuget Package Manager: -devexpress-controls-using-nuget-packages/setup-visual-studios-nuget-package-manager

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?

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.Object name: 'BookStoreDbContext'.

Also, I believe I have already tried those examples as they seem to be the same as the examples I mentioned above which was the original base of the project. There are just a few changes from testing things, but yeah.

I added it since then I haven't seen the other issue but the disposed is still occuring, the Dispose call was only added as a test as that was already occuring and once removed it continues to occur, it occurs at random but not highly frequant, I did notice when in debug it seems to occur faster.

It seems to be random for me, running it with visual studio debug, and duplicating tables and mass refreshing them seems to make the occurrence more likely, but still occurs at random either way. My current project is pretty much identical to what I last sent you as it was a test project for this issue, but it may still be easier for us to call and try reproduce this issue for you locally otherwise solve it for me by looking for environment differences etc. Since it seems to occur quite often for me.

That's weird, the only thing I can suggest is hopping on a call and work on reproducing it for you or fixing it for me together, that way we can compare environments etc. As I have no clue why you are not experiencing the issue like we are.

3a8082e126