I'm trying to build a custom ASP.NET membership provider, but I find that most MembershipProvider methods are too microscopic to integrate well with the Tessitura API functions. For example, a MembershipProvider must have a ValidateUser() method, but the closest equivalent is Tessitura's LoginEx2() method. If I have ValidateUser() call LoginEx2(), it will inadvertently log in the constituent. I also find that certain functionality is automated in a way that is incompatible with the API. The ASP.NET Login control, for example, relies on ValidateUser() to check the username and password, but handles the login / logout process for me.The only way around this that I can think of is to forgo the MembershipProvider altogether and to make custom ASP.NET web controls to use, inheriting and overriding the functionality as needed. This would unfortunately break some other convenient features of ASP.NET, such as automated user-role-based menus, and some useful features of the CMS that I'm using (Umbraco).Does anyone have any ideas of how to reconcile this situation?