universal-provider

.NET 4.5 Universal Membership Provider table names

由 浪子不回头ぞ 提交于 2020-01-02 02:20:29
问题 Is there any way to prefix the new .NET 4.5 DefaultMembershipProvider table names in the database? They used to be named aspnet_Users, aspnet_Roles etc. and they are now named just Users, Roles, etc. which is conflicting with my application schema that has a table User. Is my only option to use a separate database for membership if I want to use the new universal providers and avoid this naming issue? 回答1: Unfortunately there is no way to customize the table names for the Universal Providers

.NET 4.5 Universal Membership Provider table names

由 放肆的年华 提交于 2020-01-02 02:20:04
问题 Is there any way to prefix the new .NET 4.5 DefaultMembershipProvider table names in the database? They used to be named aspnet_Users, aspnet_Roles etc. and they are now named just Users, Roles, etc. which is conflicting with my application schema that has a table User. Is my only option to use a separate database for membership if I want to use the new universal providers and avoid this naming issue? 回答1: Unfortunately there is no way to customize the table names for the Universal Providers

ASP.NET Universal Providers and Session State

由 穿精又带淫゛_ 提交于 2019-12-11 02:28:22
问题 I'm developing an ASP.NET MVC 4 website and I'm using the Microsoft ASP.NET Universal Providers. I plan to deploy to Windows Azure and use SQL Database. In order to initialize memberships, profiles and roles on my local SQL Server 2008 database, I created a new user via the ASP.NET Web Site Administration Tool. How do I initialize sessions? When my application runs, naturally I get a SqlException saying "Invalid object name dbo.Sessions." When testing on Windows Azure, this wasn't an issue;

.NET 4.5 Universal Membership Provider table names

由 人盡茶涼 提交于 2019-12-05 03:52:39
Is there any way to prefix the new .NET 4.5 DefaultMembershipProvider table names in the database? They used to be named aspnet_Users, aspnet_Roles etc. and they are now named just Users, Roles, etc. which is conflicting with my application schema that has a table User. Is my only option to use a separate database for membership if I want to use the new universal providers and avoid this naming issue? Hao Kung Unfortunately there is no way to customize the table names for the Universal Providers currently, I'll make sure we consider adding support for this in the future. It may be possible to
订阅 universal-provider