Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jun 29, 2008 08:02 PM by Cowboy
Jun 04, 2008 05:43 PM|LINK
I'm wondering why there is User class and User Table. Can't we use Asp.net membership (MembershipUser)?
Thanks in advance,
Jun 04, 2008 06:56 PM|LINK
I will have to go back and look at that tutorial but I thought that he was leverageing the standard asp.net membership. He just had to basically write his own MVC style wrap up as he wouldn't be making use of runat = server so therfor didn't want to use
the standard controls.
Jun 04, 2008 08:34 PM|LINK
I don't want to tie the user experience to ASP membership. This goes along the lines of making the application super-extensible - imagine there are existing sites out there (usually within a corporate setting) that have their own systems in place (happens
a lot). I want people to be able to map their users easily.
That said my default is ASP membership.
Jun 05, 2008 02:30 AM|LINK
I got it. Thanks for your explanation.
Jun 29, 2008 08:02 PM|LINK
If ASP.NET Membership is important to you, you can add it. There is an MVC Membership project on CodePlex. Personally, I probably would have gone ahead and included ASP.NET Membership, but it is because I would be using it, so I guess we would call that
selfish. I understand the decision not to do it, however. I love the video series on the StoreFront. Nice stuff!