简体繁体 English

ASP.NET成员资格提供程序和Azure

[英]ASP.NET Membership Providers and Azure

原文 2013-10-17 23:27:04 8 2 asp.net/ azure/ webforms/ ado.net/ asp.net-membership

I currently have about 15 Web Forms Application (2.0+) websites on a hosted VM and I need to migrate all my client's sites to Azure shortly. 我目前在托管虚拟机上有大约15个Web窗体应用程序（2.0+）网站，我需要很快将所有客户端的站点迁移到Azure。 Several of these sites use SQL Server 2008 and the regular ASP.NET Membership Provider (some with custom profiles). 其中一些站点使用SQL Server 2008和常规ASP.NET成员资格提供程序（一些使用自定义配置文件）。 All data access in these clients' sites use ADO.NET. 这些客户端站点中的所有数据访问都使用ADO.NET。

I suspect that I need to upgrade to "Universal Providers", but I am confused by the existence of ASP.NET "Identity" and "SimpleMembership" providers. 我怀疑我需要升级到“Universal Providers”，但我对ASP.NET“Identity”和“SimpleMembership”提供商的存在感到困惑。 I'm now looking at three different providers offered by Microsoft. 我现在正在关注微软提供的三种不同的提供商。 Can someone clarify which to use and which one corresponds to the future direction Microsoft is taking? 有人可以澄清哪些使用哪个以及哪个对应于微软正在采用的未来方向？

If Universal Providers is the correct way to go, does this mean that ADO.NET code will not work? 如果Universal Providers是正确的方法，这是否意味着ADO.NET代码不起作用？ To be specific, will Universal Providers only work with Entity Framework? 具体而言，Universal Providers是否只与Entity Framework一起使用？ If this is the case, what is the best migration approach to take short of abandoning Azure completely? 如果是这种情况，那么完全放弃Azure的最佳迁移方法是什么？

2 个解决方案

ASP.NET Identity is the recommended membership system going forward. ASP.NET Identity是推荐的会员系统。 If you want to store the membership system in Azure Table storage then you should consider moving to ASP.NET Identity instead of Universal Providers. 如果要将成员资格系统存储在Azure表存储中，则应考虑转移到ASP.NET Identity而不是Universal Providers。 Universal Providers are useful if you only want to use Sql Server in Windows Azure. 如果您只想在Windows Azure中使用Sql Server，则通用提供程序非常有用。

Can someone clarify which to use and which one corresponds to the future direction Microsoft is taking? 有人可以澄清哪些使用哪个以及哪个对应于微软正在采用的未来方向？

If you are migrating old Membership Provider to new one, ASP.NET Universal Providers will be the closest one (as well as easiest). 如果要将旧的成员资格提供程序迁移到新的成员资格提供程序， ASP.NET Universal Providers将是最接近的（也是最简单的）。

does this mean that ADO.NET code will not work? 这是否意味着ADO.NET代码不起作用？

In Universal Providers, table names doesn't have aspnet_ suffix which is great. 在Universal Providers中，表名没有aspnet_后缀，这很好。 However, if your existing project accesses those tables, then you'll need to modify your source code. 但是，如果现有项目访问这些表，则需要修改源代码。

will Universal Providers only work with Entity Framework? Universal Providers是否只与Entity Framework合作？

Universal Providers uses Entity Framework code first under the hood. Universal Providers首先使用Entity Framework代码。

If this is the case, what is the best migration approach to take short of abandoning Azure completely? 如果是这种情况，那么完全放弃Azure的最佳迁移方法是什么？

As I stated, you can migrate old Membership Provider to new Universal Provider because table are one-to-one except aspnet_ suffix. 正如我所说，您可以将旧的成员资格提供程序迁移到新的Universal Provider，因为除了aspnet_后缀之外，表是一对一的。