I'm currently re-writting an entire website in .Net. The current website is written in foxpro and uses custom logic, validation rules, and Sql server tables to store and authenticate users.
I want to use Membership Provider but I have one major problem that I'm not sure how to overcome.
Both, the new site and the old site have to share users and credentials. The users will have to be able to use both sites during the transition phase without having to update their profiles separately.
What is the best way to implement Membership Provider without breaking the existing system?
Do I have to use all the tables, views, procedures, etc that come with Membership provider?
Is my logic flawed? Is Membership Provider worth it?
Any tutorial or video links are much appreciated.