Mar 18, 2012 at 8:19 AM
Edited Mar 18, 2012 at 8:22 AM
You do NOT want the membership provider in here. We just ripped that trash out of an applicaiton because it's a boated pile of shit. Custom authentication providers..role your own. It's been done a hundred times on GOOD teams. And
there's a reason for it...it's not bloated and it only takes a few classes to create one. Find someone who has and get their code and understand WHY you do not want to keep resortingto the stupid ASP.NET Memberhip crap provider.
Please do your research, don't just take whatever bells and whistles Microsoft throws at you. A lot of it is BLOAT and PAIN. Yes sometimes you have to code developers... YES.
If you want some example code of a custom auth provider I would be happy to provide it to you mxmissle but please do not advocate the pile ASP.NET Membership provider and its 15 tables, 15 views and BLOATED heavy, overcomplex framework structure.
The problem with the .NET community is that a lot of developers are not exprienced enough or will never be on a team where the light shines and you see why certain teams and ecommerce sites do not use crap like the ASP.NET Membership provider. Why
good teams know that using ALL stored procs as the basis to CRUD your application is trash (use LINQ to SQL, another ORM that is NOT Entity Framework, or use parameterized SQL calls from your C# code). Parameterized, this is not the old inline SQL that
was "bad" back in the day. Do your research. And PLEASE PLEASE DO NOT USE MS DATASETS...pile of shit.