To Team please;
I have an application under development using ASP.Net 4.0 WebForm, which uses the legacy membership heavily for authentication and authorization. As .Net 4.5.1 is emerging I want to bring my existing app to .Net 4.5.1 to stay current with .Net version. However, with the news (and the same time lack of clarity) of the new membership in Net 4.5.1, it has caused a great deal of concern and confusion for me and how it will affect the current use of membership system and how it will be compatible with the new Membership.
Could someone please, explain to me what compatibility issues I'll be facing or are they even compatible or do I have to start from scratch with the new membership?
Just to provide more info about the security and membership within this app. Half of this app is being written in WebForm as business data entry system and the second half, will be written either in WebAPI or MVC to support Mobile. Both parts of this app must use one set of membership and user files.
I greatly appreciate any info of guidelines to help this ambiguity.
Thanks!
..Ben