what is the difference between identity and sql membership

Question

User264732274 posted

why identity  come into scene ? what was the draw back of sql membership ?

what can be done by identity which is not possible by sql membership ?

thanks

Answer 1

User753101303 posted

Hi,

This is pretty well described here:  http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity,

I talked about both not knowing which VS and .NET Framework version you are using.

Answer 2

User264732274 posted

i am working with VS2013 IDE.

the link u gave it seems it will talk about identity area not member ship.

identity and membership both drop auth cookie in client pc ?

tell me where to find code in mvc project which drop auth cookie when working with identity or membership ?

thanks

Answer 3

User614698185 posted

Hi sudip_inn,

ASP.NET membership gives you a built-in way to validate and store user credentials. ASP.NET membership therefore helps you manage user authentication in your Web sites. You can use ASP.NET membership with ASP.NET Forms authentication or with the ASP.NET login controls to create a complete system for authenticating users.

For more information, please see: https://msdn.microsoft.com/en-us/library/yh26yfzy(v=VS.100).aspx

ASP.NET Identity is latest membership technology. ASP.NET identity works only with .Net Framework 4.5 or later. If for some reason you must use .Net Framework 2.0 or 3.5 then you have to stay with old Membership or SimpleMembership systems.

New ASP.NET Identity is released as NuGet package and also included by default in Visual Studio 2013. Publishing in form of NuGet package helps to obtain new versions easier in the future. ASP.NET Identity is located in Microsoft.AspNet.Identity.Core namespace.

Please see: ASP.NET Identity new features and advantages

Best Regards,

Candice Zhou

Answer 4

User753101303 posted

It starts by discussing ASP.NET membership before. For example you can't use exxternal identities (Microsoft, Faceboook etc...), you can't customize the db schema  (unlike ASP.NET identity) etc... It then still discuss one or two other older options and then only explains how to use ASP.NET identity wiht some code. Have you tried?

Answer 5

User264732274 posted

@Patrice i heard db table schema is possible when people work with identity but for that some one has to know EF code first migration. suppose if some one not familiar with EF code first migration then how they can change db schema when working with identity.

please guide. thanks

Answer 6

User753101303 posted

EF migration is unrelated to ASP.NET Identity. It is just a tool which allows to programmatically upgrade a database schema to the next version but you are free to use it or not. If creating a database you don't need it. I don't see also wh you coudn't even use a "code first with existing database" if you want etc...

Answer 7

User264732274 posted

@Patrice u said "EF migration is unrelated to ASP.NET Identity"

so redirect me to few right article which guide me in details how to upgrade asp.net identity db schema without EF migration usage.

thanks

Answer 8

User753101303 posted

To be on the safe side, could you confirm that you are just implementing ASP.NET identity in a new database. This is my understanding about your current situation from the past discussions.

"upgrade asp.net identity db schema" would be rather the case where you previously implemented ASP.NET identity and want to do schema changes on existing table for a new version (so once again I believe this is not your current situation).