|
Do you have any links to the articles?
|
|
|
|
|
|
gone
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Gone
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
|
Gone
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
This article[^]
Your opinions please.
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
modified 13-Nov-15 18:41pm.
|
|
|
|
|
|
|
Gone
I never finish anyth
|
|
|
|
|
|
Gone
I never finish anyth
|
|
|
|
|
|
|
|
|
|
|
|
Dead
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Aha, thank you.
—SASergey A Kryukov
|
|
|
|
|
|
I got ride of it
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Article: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?waid=190464&aid=1055096[^]
User: http://www.codeproject.com/script/Membership/View.aspx?mid=11678231[^]
Copied from various sources.
Source http://www.beansoftware.com/ASP.NET-Tutorials/identity-membership-simplemembership.aspx[^]: Quote: First, ASP.NET Membership system is hard to customize. It uses SQL Server database only to store data about users. It has predefined user's information table that will be stored. It is not simple to extend default functionality and add custom user fields, or to move data to other kind of database. Membership database schema is designed for SQL Server only. It is hard to move data to other data sources, especially to non-relational databases.
Article:
Quote: ASP.NET Membership system is hard to customize. It uses SQL Server database only to store data about users. It has predefined user's information table that will be stored. It is not simple to extend default functionality and add custom user fields, or to move data to other kind of database. Membership database schema is designed for SQL Server only. It is hard to move data to other data sources, especially to non-relational databases.
Source https://msdn.microsoft.com/en-us/library/yh26yfzy.aspx[^]:
Quote: Each time the user requests a page, ASP.NET forms authentication checks whether the user is authenticated. If a page is restricted, users who are authenticated and are members of the approved roles are allowed to view the page. Anonymous users (users who are not logged in) are directed to the login page. By default, the authentication cookie remains valid for the user's session.
After a user has been authenticated, the membership system makes available an object that contains information about the current user. For example, you can get properties of the membership user object to determine the user's name and email address, when the user last logged into your Web site, and so on.
Article:
Quote: Each time the user requests a page, ASP.NET forms authentication checks whether the user is authenticated. If a page is restricted, users who are authenticated and are members of the approved roles are allowed to view the page. Anonymous users (users who are not logged in) are directed to the login page. By default, the authentication cookie remains valid for the user's session.
After a user has been authenticated, the membership system makes available an object that contains information about the current user. For example, you can get properties of the membership user object to determine the user's name and email address, when the user last logged into your Web site, and so on.
|
|
|
|