管理另一个应用程序的ASP.NET成员资格 [英] Managing ASP.NET Membership of another application

查看:94
本文介绍了管理另一个应用程序的ASP.NET成员资格的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个建筑难题.

我需要从另一个ASP.NET Web Forms应用程序管理现有ASP.NET Web Forms应用程序的用户.这两个应用程序都有自己的数据库和成员资格的实现.

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.

我想到了通过带有CORS的Web服务远程进行操作的想法.但是,有什么办法可以在同一个VS解决方案中做到这一点吗? IE.向其中添加另一个项目(仅用于管理其他应用程序的用户).有没有办法为类库项目添加成员资格功能?具体来说,我只是追求基本的CRUD功能.

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.

推荐答案

它们是否在同一解决方案中,似乎与从单独的Web应用程序管理它们没有多大关系.在数据库上集成将限制Web应用程序.

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.

一个Web服务是理想的.我建议该Web服务与在下面使用成员资格提供程序的事实无关.随着您的Web应用程序的进步,您可能需要切换到另一个身份验证系统(例如移至.NET Core).因此,您在两个应用程序之间拥有更多的依赖关系,这意味着它们都必须一起更改.通过网络服务隔离意味着它们可以独立进行.

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.

这篇关于管理另一个应用程序的ASP.NET成员资格的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆