Home/ Questions/Q 8431141
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T05:46:36+00:00

I am implementing a custom ASP.NET membership provider that operates based on the custom

  • 0

I am implementing a custom ASP.NET membership provider that operates based on the custom repository class that in turn uses an Entity Framework DbContext as a mean of accessing a data.

Since this is an ASP.NET MVC application, IoC container (Ninject) is set to resolve instances of my DbContext InRequestScope.

My user data tables are a part of the single main DbContext.

Repository class is also bound to instantiate in InRequestScope. But the repository class is created by to satisfy the need of the custom MembershipProvider, which can’t be set to instantiate InRequestScope. As a result, whenever I am trying to access Role data via repository, I get DbContext is already disposed exception.

Has anyone set up a similar configuration and if so, what was implemented differently to overcome the problem I am having. Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A workaround that has allowed me to continue with the project development was to manually create an instance of DbContext in Membership Provider constructor, in contrast to have Ninject inject it.

    Maybe someone eventually will come up with a better approach to this particular problem, please post it here and I will remark it as an answer instead of this workaround.

    • 0