Custom Membership Api.Im confused the more i search on the net
-
hello fellas! "Please i know this is a recurrent question. but i need some explanation.Please" i'm a bit new and on probation period.Been giving a project to build a site registration system with Membership API.Please remember i'm new so please be easy.After reading atricles from the net and post from forums to forums. I made a change to the database with the aspnet_regsql.exe tool and stuff.All i need to do is to be able to store additional users information in another table create for that. After reading this cool article from http://www.devx.com/codemag/Article/34492/0/page/1 i decided to go for this model since i have only to care about consist data in my additional table. that model constist of inheriting classes like MembershipProvider, MembershipUser, etc and create custom functions for exemple creauser which will call the membership createuser then return the UserId to then use it to insert to my additional table.The fact is after reading those articles with differents approaches really confuses me more.Added the fact that i have done anything with security namespace. So far it obvious to create my inheriting classes like.MySqlMembershipProvider, MyMembershipUser and MyMembership(for my methods create or GetUser).But from reading people creates classes like TheirConfiguration TheirProviderCollection.it confuses me.Can any one tell me which classes i really need for my schema ie one additional table?thanks
eager to learn
-
hello fellas! "Please i know this is a recurrent question. but i need some explanation.Please" i'm a bit new and on probation period.Been giving a project to build a site registration system with Membership API.Please remember i'm new so please be easy.After reading atricles from the net and post from forums to forums. I made a change to the database with the aspnet_regsql.exe tool and stuff.All i need to do is to be able to store additional users information in another table create for that. After reading this cool article from http://www.devx.com/codemag/Article/34492/0/page/1 i decided to go for this model since i have only to care about consist data in my additional table. that model constist of inheriting classes like MembershipProvider, MembershipUser, etc and create custom functions for exemple creauser which will call the membership createuser then return the UserId to then use it to insert to my additional table.The fact is after reading those articles with differents approaches really confuses me more.Added the fact that i have done anything with security namespace. So far it obvious to create my inheriting classes like.MySqlMembershipProvider, MyMembershipUser and MyMembership(for my methods create or GetUser).But from reading people creates classes like TheirConfiguration TheirProviderCollection.it confuses me.Can any one tell me which classes i really need for my schema ie one additional table?thanks
eager to learn
If you are new forget about all that stuff that you read on that article
highjo wrote:
that model constist of inheriting classes like MembershipProvider
Forget about it and use as it is
highjo wrote:
All i need to do is to be able to store additional users information in another table create for that.
For this, the easiest way is to store this info using profiles, if you dont want to use profiles, create your custom table and add a userName field to it, so that you can know to which user that record belongs to But dont modify the aspnet_XXX tables
Alexei Rodriguez
-
hello fellas! "Please i know this is a recurrent question. but i need some explanation.Please" i'm a bit new and on probation period.Been giving a project to build a site registration system with Membership API.Please remember i'm new so please be easy.After reading atricles from the net and post from forums to forums. I made a change to the database with the aspnet_regsql.exe tool and stuff.All i need to do is to be able to store additional users information in another table create for that. After reading this cool article from http://www.devx.com/codemag/Article/34492/0/page/1 i decided to go for this model since i have only to care about consist data in my additional table. that model constist of inheriting classes like MembershipProvider, MembershipUser, etc and create custom functions for exemple creauser which will call the membership createuser then return the UserId to then use it to insert to my additional table.The fact is after reading those articles with differents approaches really confuses me more.Added the fact that i have done anything with security namespace. So far it obvious to create my inheriting classes like.MySqlMembershipProvider, MyMembershipUser and MyMembership(for my methods create or GetUser).But from reading people creates classes like TheirConfiguration TheirProviderCollection.it confuses me.Can any one tell me which classes i really need for my schema ie one additional table?thanks
eager to learn
Can't you use the built in profile provider for this?
Nirandas, a developer from India. http://www.nirandas.com