Using: CreateUserWizard and Standard SQL Database Provider Model
The client would like the account's username to be the user's email address.
Both the CreateUserWizard and the SQL provider database seperate these out into two different fields.
I could probably handle the account creation easily by injecting the email into the username, but I am worried about other logics such as editing accounts and teh Forgot My Password page.
Is there a standard practice for this or an article I can be pointed towards?
Thanks
...
Go to the complete details ...