Will MembershipProviders be re-written?
Here’s a list of abstract methods I have to implement on my custom MembershipProvider which aren’t applicable since I’m planning on using CardSpace as my login mechanism which doesn’t have any passwords:
bool ChangePassword(string username, string oldPassword, string newPassword)
bool ChangePasswordQuestionAndAnswer(string username, string password, string newPasswordQuestion, string newPasswordAnswer)
bool EnablePasswordReset
bool EnablePasswordRetrieval
string GetPassword(string username, string answer)
int MaxInvalidPasswordAttempts
int MinRequiredNonAlphanumericCharacters
int MinRequiredPasswordLength
int PasswordAttemptWindow
MembershipPasswordFormat PasswordFormat
string PasswordStrengthRegularExpression
bool RequiresQuestionAndAnswer
string ResetPassword(string username, string answer)
Not that it’s a train-smash to put some default values in or throw a NotImplementedException but I wonder if we’ll see a change in the MembershipProvider abstract class for feature version of ASP.NET.
On a side note, although .NET has a NotImplementedException (since .NET 1.1) why does Visual Studio throw a general exception with the message “The method or operation is not implemented.”?



I’ve found the answer here (http://blogs.msdn.com/ansonh/archive/2005/12/08/501763.aspx) and its due to backward compatibility with the Compact Framework 1.0 that doesn’t implement NotImplementedException.