问题
I have an architectural dilemma..
I need to be managing an existing ASP.NET Web Forms application's users from a different ASP.NET Web Forms application. Both apps have their own databases and implementations of Membership.
I've toyed with the idea of doing it remotely via a web service with CORS. But is there any way I could do it from within the same VS Solution? Ie. add another project to it (for the sole purpose of managing the other app's users). Is there a way to add features of Membership to a Class Library project maybe? Specifically I'm only after the basic CRUD features.
回答1:
Whether they are in the same solution or not doesn't seem to have much to do with managing them from separate web apps. Integrating at the DB will restrict the webapps.
A webservice is ideal. I'd suggest the webservice is agnostic of the fact it's using membership provider underneath. As your web apps progress you may want to switch out the authentication system with another ( Like moving to .NET Core ). So the more dependencies you have between both apps means they both have to change together. Isolating via webservices means they can independently progress.
来源：https://stackoverflow.com/questions/42099888/managing-asp-net-membership-of-another-application