Geek Answers Handbook

ASP.NET profiles and memberships are custom providers or should I roll back completely?

At first I know that this question can be borderline-duplicated to this , and yes, it’s a little ironic that I ask a question about something that I even answered myself.

Now I'm talking about ASP.net profiles. I am building an application using MVC if that matters, and I find the built-in profile provider to be useless.

So, at the moment, I ask myself the question: should I follow my own advice and write my own profile provider, or do I need to completely flip my own profile?

Some assumptions:

  • I need my data in the database structure, which I solve
  • This is a completely new application that does not have an outdated database structure or user database that needs to be integrated.
  • Small and medium number of users (no more than ~ 5000 users)
  • ASP.net MVC is most likely Silverlight 2 and possibly even Windows Azure, but I'm still experimenting with it, but definitely .net 3.5 SP1.
  • And perhaps as a basic solution: it is not necessary to use Forms Auth, the application may end up using Active Directory or OpenID for authentication

, ASP.net (OpenID), , ASP.net , ASP.net, OpenID ( ) .

, , , , , , , , - , / , , , -, ?

+5
2

, . ( , ). , , GetUser() ValidateUser().

, ( ) , , GetUser() , , .

+3

, , , , , .net. , , , yuo .

, : " x, y z , ?"

0

More articles:


All Articles