Home/ Questions/Q 7059593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T04:15:02+00:00

I am building a project using ASP.Net 4 and MVC3 using C#. The ASP.Net

  • 0

I am building a project using ASP.Net 4 and MVC3 using C#.
The ASP.Net Membership Provider is integrated well into the framework.
Role check and some identity information but I have an issue.
It’s limited flexibility.
Should I build a new user management system from the ground up and lose the convenient short codes within controllers ect….?
Are there any alternative?

Worry about hashing passwords, caching stuff, session management just gives me a headache when I think about building something from scratch.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I use the ASP Membership mainly for logging-in (only). Then I use database-specific tables for highly-customized user-features that ASP Membership doesn’t easily accomodate (or at all). If any custom-feature “can” be (easily) accomodated by the ASP Membership Db…then I use it…but mostly, I put custom user-specific functionality in the target database (in-question).

    Also…

    Because the ASP Membership functionality can manage many databases at the same time, I run a separate ASP Membership database instance (apart) from those it manages. Doings so has proven clean & friendly for me.

    • 0