I am going to design my Login page and I won't use the Login control because of some logic I need to take into account.
My questions are:
-Must I keep on using the MembershipProvider model?
-Can I go direct through the Custom Principal and Identity passing over the MembershipProvider class?
-Is the MembershipProvider useful only when a asp:login control is used? Thinking that the asp:login control ask for the default MembershipProvider.
Thanks in advance
CSLA doesn't really care, as long as you end up with a valid principal, and as long as you can restore that principal on every page request through global.asax. Nothing in CSLA is tied to any specific authentication model, MembershipProvider or otherwise.
Copyright (c) Marimer LLC