title: ASP.NET Identity vs Simple membership Pros and Cons?
body: <p>In MVC4 we had <strong>Simple Membership</strong>. My opinion is that Simple Membership was a good Identity Model tried and tested with good documentation and didn't need to be fixed but simply needed an upgrade in terms of <strong>Email Verification/ Password Reset</strong> and all other stuff that we normally have to deal with when building an app. However the new  ASP.NET Identity model seems achieve Something of sorts that Vista achieved over XP. I mean <code>AspnetUserClaims</code> and <code>AspnetLogins</code> could have been bunched together as <code>UserAliases</code>. And Microsoft should have provided some methods for the Email part of my babble. Having just discussed my opinion based on first looks which might be deceiving my question is</p>
  
  <p>I am trying to decide whether I should move from <strong>Simple Membership</strong> to the new  <strong>ASP.NET Identity</strong> but since documentation and tests of  ASP.NET Identity model is sparse, conflicting and hard to locate using Google. So can someone with experience of both please summarize the pros and cons?</p>