Is there another (preferable simpler) way of including membership tables in your own database other than writing your own provider?
Is there another (preferable simpler) way of including membership tables in your own database
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there another (preferable simpler) way of including membership tables in your own database other than writing your own provider?
Of course you can deploy the MS membership provider into whatever database you like (provided that it uses SQL Server). You can use the command-line tool aspnet_regsql.exe (located in the framework folder) to create the tables and procedures used by the membership provider. You won’t be able to use your own tables without changing the either the stored procedures or writing your own provider but you can extend the tables (for example adding foreign keys to the users table or adding columns).
I believe you can setup a connection string in the web.config and deploy the tables via web interface but I’m not entirely sure about that. However I am absolutely sure that once deployed you can tweak your existing database with the web tool if you setup the connection string.