0

I have been doing some research about how to do custom profileprovider in .NET MVC. It seems pretty complicated. Is there any other alternative? And this is my major concern, why do ppl bother using customer profileprovider? If they want extra information about a user, why don't they just make another table with OneToOne relationship with aspnet_Users with userId or userName as the foreign key?

Please clarify. I'm trying to implement user profile functionality, but I don't wanna go down the wrong path.

Thanks DG

Dhana
  • 371
  • 4
  • 17
  • You don't need a 'custom' profile provider unless you're doing some complex business logic or pulling data from a different data structure. The tables should be provided for you if you've used the `aspnet_regsql.exe` utility. Then, just use the [SqlProfileProvider](http://msdn.microsoft.com/en-us/library/system.web.profile.sqlprofileprovider.aspx) class that comes with the framework. – Joseph Yaduvanshi Nov 30 '11 at 03:49
  • No. I dont wanna do SqlProfileProvider. I'll be querying lots of data in and out – Dhana Nov 30 '11 at 04:17

1 Answers1

1

(not to sure if this helps talk about custom profile providers.. unless I'm misunderstood...)

IMO, what ever you do .. avoid (the baked in) ASP.NET Membership at any cost! It's sooooo over engineered, you'll want to stab yourself in the eye with a blunt spoon :(

Trust me. avoid it.

Why: Should I use the built-in membership provider for an ASP .NET MVC application?

So .. what can we do instead?

It's just so simple to roll your own Username/Password and leverage the built in Forms Authentication. For myself, I'm not a fan of storing -any- passwords in my own database .. so i prefer to use Facebook, Twitter or OAuth as my mechanism for authentication .. which then means I finish up with a simple, basic, custom user class.

I also create my own custom IPrincipal and IIdentity because I want to store a bit more info in the cookie, which Forms Auth creates when a person has been authenticated. This then helps keep my code in my Controllers cleaner and way simpler.

For example, I store the userId of the authenticated person in an encrypted cookie. (the default option is to only store a Name). I also store one or two more things .. but you get the idea. This way, I don't always have the hit the DB to retrieve any user data OR store this crap in a session.

With a roll your own, u can create extra meta data (birthday? mum's maiden name? social security number (joke) ) .. and have that extra profile data. Same table? extra table? who cares ... that's a decision to make way later (and EASY to solve). Get your model right, IMO :) Then once u've locked down your model, you now know what's required and what's optional .. and u can make some DB decisions then.

TLDR??

  1. Avoid the built in ASP.NET Membership crap
  2. Roll your own .. and keep it simple.
  3. If you're feeling advanced, also roll your own IPrincipal and IIdentidy to really rock your world.

GL HF and don't stab yourself with a blunt spoon, in your eye!

enter image description here

Community
  • 1
  • 1
Pure.Krome
  • 84,693
  • 113
  • 396
  • 647