难道大多数人使用.NET的SqlMembershipProvider的，SqlRoleProvider和的SqlProfileProvider？ [英] Do most people use .NET's SqlMembershipProvider, SqlRoleProvider, and SqlProfileProvider?

问题描述

大部分人都使用.NET的SqlMembershipProvider的，SqlRoleProvider和发展的SqlProfileProvider成员与功能的网站是什么时候？

Do most people use .NET's SqlMembershipProvider, SqlRoleProvider, and SqlProfileProvider when developing a site with membership capabilities?

还是有很多人做出自己的供应商，甚至是自己的会员系统完全？

Or do many people make their own providers, or even their own membership systems entirely?

什么是SQL提供商，将让你​​滚你自己的局限性？

What are the limitations of the SQL providers that would make you roll your own?

时很容易扩展SQL商提供额外的功能？

Is it easy to extend the SQL providers to provide additional functionality?

仅供参考

每斯科特谷的博客，<一个href=\"http://download.microsoft.com/download/a/b/3/ab3c284b-dc9a-473d-b7e3-33bacfcc8e98/ProviderToolkitSamples.msi\">Microsoft提供了源$ C ​​$ C为SqlMembershipProvider的，让你可以自定义的，而不是从头开始吧，。只是一个供参考。

For Reference
Per Scott Gu's Blog, Microsoft provides the source code for the SqlMembershipProvider so that you can customize it, instead of starting from scratch. Just an FYI.

推荐答案

我们用除配置文件提供的一切。该配置文件提供基于完全地文字和确实全文seearches - 这将成为你的用户群变得更大极其缓慢。我们发现这是一个更好的解决方案，以角色我们自己，即键入到会员的用户ID成员API数据库资料部分。

We use everything except the Profile Provider. The Profile Provider is completly text based and does full text seearches - this becomes exceedingly slow as you user base gets larger. We have found it a much better solution to "role our own" profile section of the membership api database that is keyed to the userid in membership.

这篇关于难道大多数人使用.NET的SqlMembershipProvider的，SqlRoleProvider和的SqlProfileProvider？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！