Migrating to Csla 6 - DI Scope management #3599
Unanswered
ajohnstone-ks
asked this question in
Questions
Replies: 1 comment 3 replies
-
You should no longer need to manage the DI scope yourself. Because CSLA 6+ fully incorporates DI, there is a DI scope created/disposed for every server-side data portal operation. It might be that this doesn't fully work until CSLA 7 - we did fix some bugs around this and I don't remember specifically when. (as an aside, I'd personally just skip CSLA 6 and go for 7 - there are few breaking changes, and many improvements!) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In Csla 5, we implemented
IInterceptDataPortal
so that we can create anIServiceScope
that lives for the lifetime of a "root" level data portal call. To do that it was settingApplicationContext.ServiceProviderScope
That doesn't work anymore, because
ApplicationContext
is no longer static, and no longer has that property.Where do I need to plug into now to handle the scope creation/disposal?
Beta Was this translation helpful? Give feedback.
All reactions