Is a .Net membership database portable, or are accounts somehow bound to the originating Web site or
- by Deane
I have an ASP.Net Web site using .Net Membership with a SQL Server provider, so the users and roles are stored in the SQL tables created by Aspnet_regsql.exe.
Is this architecture totally self-contained and portable, or are users in it somehow bound to the specific Web site on which they create their account?
Put another way, if we create a bunch of users in dev or UAT, the back up and restore this database to another server, accessed under another domain name, should it still work just fine?
We're seeing some odd behavior when we move the database, like users losing group affiliation and such, and I'm curious how portable and environment-agnostic this database really is. I have a sneaking suspicion that something is bound to the machine key or the domain.