Not corrected DbContext initialization (memory leaks)...

[nocher]

Hi just have checked sources, have found following things:

• some code, which is working with DataContext, don't execute context.Dispose() method (role & membership providers)
• is better to use using code directive, which autmaticaly call dispose for disposable objects

• table mappings:

   - in my case i have backend and frontend applications, 
   - both have one database connection/context
   - i want to have separate tables for backend and frontend users

  that is why is good to have extra configuration attributes for membership and role providers:

  userTableName = config.GetConfigValue("userTable", settings.UserTable ?? "Users"); roleTableName = config.GetConfigValue("roleTable", settings.RoleTable ?? "Roles");

if you provide me rights - i could submit those changes. or could provide you sources, which have been modified.

[holyprin]

Sure, ill give it to you. Technically you dont need using blocks if you need to fine grain manage the disposable objects in async code. Though this is not async and is amazingly old code. I however have completely moved away from using entity framework as it is bounds slower then raw sql and micro orms. (Dapper / Insight.Database)

On Apr 2, 2013, at 7:19 AM, nocher notifications@github.com wrote:

Hi just have checked sources, have found following things:

• some code, which is working with DataContext, don't execute context.Dispose() method (role & membership providers)

• is better to use using code directive, which autmaticaly call dispose

  for disposable objects

  table mappings:

  • in my case i have backend and frontend applications,
  • both have one database connection/context
  • i want to have separate tables for backend and frontend users

  that is why is good to have extra configuration attributes for membership and role providers:

  userTableName = config.GetConfigValue("userTable", settings.UserTable ?? "Users"); roleTableName = config.GetConfigValue("roleTable", settings.RoleTable ?? "Roles");

if you provide me rights - i could submit those changes.

— Reply to this email directly or view it on GitHubhttps://github.com/holyprin/Holyprin.Web.Security/issues/7 .

[holyprin]

I am confused as to why you wouldn't just add a column to the users and roles tables that controls backend / frontend users.

[nocher]

• I have to be sure 100% that only backend users have access to backend functionality, frontend users - frontend functionality.
• Also i have to have possibility to map ORM Model as simple as possible (without performance issue: no view/ extra sql queries etc).

[holyprin]

Sure if you want to submit a pull request from your fork ill be glad to look it over. Again while this project was a priority to me i have since learned much faster ways then entity framework. Plus im amost entirely dealing with c/objective-c now, project has basically been shelved.