Geek Answers Handbook

What to use for ASP.NET membership

I am not very good at using ASP.NET, but I used the built-in membership providers for a simple WebForms application, and I found their PITA when trying to expand the way they work (add / remove multiple fields and repeat accordingly). Now I am preparing for the MVC project (ASP.NET MVC or Monorail), and I think - is there a better way to handle users? Ask them to log in / log out, save certain parts of the site for specific users (for example, registered users or something similar to the “share this with friends” feature on many social networking sites where you can designate users with access to certain things: what is the best way to make it scale well?

I guess I wasn’t so understood. To rephrase my question: Would you use a standard ASP.NET membership provider for a website-oriented application, or something else (what)?

+5
source share
4 answers

The ASP.NET membership provider is very convenient and extensible. Just use off-the-shelf features like Active Directory, SQL Server, and OpenLDAP. The main advantage is the ability to not reinvent the wheel. If your needs are more nuanced than you can create your own provider, expanding the redefinition of the methods used by ASP.NET controls.

- . . , .

:

, - , , .

+13

ActiveDirectory ? , , OpenLDAP? , , "" ..

0

.

, Active Directory OpenLDAP .

, aspnet_regsql. .

0

keep certain parts of the site accessible to certain users (for example, in a magazine in users or something similar to the “share this with friends” function, many social networking sites

I think you should customize your code.

I also don't like the asp.net membership and user code needed for my membership ...

A good membership provider is really missing the asp.net side ...

0
source

More articles:


All Articles