The reason I'm asking about this, I suspect that the set of input controls is cumbersome to use / configure. For example, I would suggest that it would be difficult to tell the user that their password is incorrect.
I tried using them, and after a while I was eventually left with only the control itself. All the authentication and user management logic was written from scratch. I simply did not want to use the default MemberhipProvider that comes with VS.
CSS, , , , Authenticate.
, , . - , .
, . , : -)
User, UserPermission, UserNotFoundException, UnauthorizedException .. , . MVC, MVC.
User
UserPermission
UserNotFoundException
UnauthorizedException
. , . - - .
, , , .
This can be done very easily. Properties FailureAction / FailureText / FailureStyle are your friends.
Why reinvent the wheel. I use the built-in controls provided by asp.net, for any custom functions I just inherit the built-in controls.
Hooray!
I use OOB input controls (combined with some style) and spend my time on the actual content of the application. In the same way, I do not invent my own journal every time I create an application.