While working on a new project with MVC3, a DI framework (Ninject), and unit tests (NUnit) paired with mocks (Moq), I found setting up the Membership Provider felt a bit "awkward". I've run into tasks ...
Are there are any specific rules and regulation to follow while developing a custom membership provider. Like, implementing a particular Interface or Abstract class. Or a definite model architecture ...
Recently, I posted the following question on SO: http://stackoverflow.com/questions/7197337/using-asp-net-membership-provider-with-an-existing-user-database As you may notice, I ended up answering my ...