|
| FelixRMelendez : On August 05, 2008 12:30 AM said: |
Joe,
This series has been great! so far, so good, but... how about showing an example of extending membership by using new properties? I mean adding a some new attributes to certain table and then being able to read such values and then displaying them in a web page?
:-)
|
|
|
| Matt3.5 : On August 05, 2008 4:28 AM said: |
Felix, you would use the profile provider for that. There are other videos showing that on asp.net and articles on msdn. If you do not want to use the blob approach you can also use the table/sproc profile provider. For a start it would be better to do this than add additional columns to the membership tables otherwise you could go over the page size (in sql server) and this will effect performance as sql server will split pages. For this reason it is better to encapsulate additional profile data in a different table and FK it to a particular userID.
|
|
|
| guru_sarkar : On August 06, 2008 4:21 PM said: |
just an idea ... moving this video to #8 from #10 would make a bit more sense.
|
|
|
| azamat : On August 07, 2008 2:22 AM said: |
It gets stop after 08.47 minutes :(
|
|
|
|
|
| mtalam : On August 27, 2008 9:34 AM said: |
Hi Joe and all friends,
Need your help to have some understanding.
I have an application at ASP 3.0, planning to move it to .net 3.5 with membership.
The question is, should i keep membership table in separate database and application at separate or all should be in one.
If separate database, then how we create referncial integrity b/w two separate database using userid field.
If same database for membership and application, then which table should be used to create refrencial intrigity.
Please guide.
Thank you
MTA.
|
|
|
| asater : On August 29, 2008 6:52 AM said: |
Hello Mtalam,
you better off posting your question on the Forums, you get a fast answer.
Thank you Joe for the video
|
|
|
|
Leave a Comment
You must be logged in to leave a comment. Click here to log in.