I got some general directin on this in an earlier question, which I appreciate. Now I'm working at the detailed design level, and I'd like to ask for opinions and ideas about whether what I'm thinking about is feasible and reasonably efficient, before I commit to coding it.
I'd like to use ASPNETDB functions primarily for user setup, login, password validation and retrieval in order to a) to not "reinvent the wheel", b) to save some of my newbie programming neurons for other tasks, and c) at least have some sense that these functions are done "right". I'm going to redundantly store userID and password my own DB files, along with all other information about the user (ie profile, roles). I'm planning to add the ASPNETDB files to my own DB to simplify DB deployment management at little. I've got that part figured out.A) & ...
Go to the complete details ...