tags:

views:

36

answers:

1
Q: 

Any downsides to using the ProfileProvider in ASP.NET

Hey everyone,

Are there any downsides like performance or gotchas in terms of functionality to using the built in ProfileProvider with .NET?

I will be storing office information, extra security questions, etc. Nothing to outrageous so it could be a good fit.

+1  A: 

It's not bad for novices, but I think it's tied to the whole membership and roles providers, which I have found to be needlessly cumbersome.

Josh Pearce  2009-11-25 02:08:31
Cumbersome in which way?
chopps  2009-11-30 03:12:45
When you install the Sql Server schema for the membership and roles providers, the top level object is an application, and I guess the thinking is that you will have multiple "applications" running against the same database. I have implemented some providers from the interfaces, that was more what I found to be cumbersome.
Josh Pearce  2009-11-30 12:41:10
Thanks for the reply Josh.
chopps  2009-12-01 17:01:02

related questions

Improve performance on ProfileManager.GetAllProfiles when using SqlProfileProvider
Caching the profiles from SqlProfileProvider -- ProfileManager.GetAllProfiles result
Do most people use .NET's SqlMembershipProvider, SqlRoleProvider, and SqlProfileProvider?