RE: Membership.ApplicationName and thread safety.
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Fri, 01 Sep 2006 11:19:08 GMT
Hi MrGrundh,
Yes, since the LoginControl will always use the default provider, we need
to programmtically do the authentication/validate user here. And I think
"OnLoggingIn " event is a workable one if you still want to make use of the
login control as the login user interface.
Please feel free to let me know if there is anything else you wonder.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- References:
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- Prev by Date: Re: Forms Authentication Problem
- Next by Date: ActiveDirectoryMembershipProvider - User properties not set
- Previous by thread: RE: Membership.ApplicationName and thread safety.
- Next by thread: RE: Membership.ApplicationName and thread safety.
- Index(es):