ThePatriot

I think I have answered this question.  It appears I can roll my own MembershipProvider and that should be fully customizable.

How can I use ASP.Net Authentication where I only need login and registration but with different table names.  In fact, we have a table that stores a person's information including email address (also their user name), password and role.  Where is it in the Silverlight project that tells the Application to use those specific tables with those default names?

I found the answers to my questions in the non-video version of this tutorial.  I also determined that the login I originally added was indeed added but to the default instance of SQLExpress.  So the non-video version of this tutorial resolved that question also.

Up to this module the tutorial has been outstanding.  But I agree with CM.  This is useless information if I can't deny an unauthorized user access to whatever resources I want to protect.  I am very familiar with Forms Authetication where everything happens in the GAC and webconfig file.  Now I wold like to know how to customize it to work in Silverlight.

In fact, when I tried to login by just running the application I got an error stating SQLExpress database could not be found (even though the event information was successfully pulled and displayed).  I expected a User Not Found or Invalid Username/password error message.  When I registered as a new user, I was able to login but I could not find any such record for me in the SlEventManager.mdf database.

I especially need to learn how to make it work with an existing SQL 2008 database which already has membership information (user name & password).  So I want it verify and add users to that table.

Great tutorial.  I have tried several books and they all pale in comparison to this tutorial.

You could save us a lot of frustration by giving us  a shot of your using statements at the start of each module.

So where are you in the process of Co-Evolution?  When will both languages be equal?