DotNetStories
In this post I will continue my series of posts on caching.
You can have a look at this post , this post , this post and this one.My last post was on Application state management and you can read it here.
I have explained some of the state mechanisms that we have in our disposal for preserving state in ASP.Net applications in various posts in this blog.
This is the fourth post in a series of posts regarding ASP.Net built in membership functionality,providers,controls. You can read the first one here .You can read the second post here . You can read the third post here.
This is the third post in a series of posts regarding ASP.Net built in membership functionality,providers,controls. You can read the first one post one here .
This is the second post in a series of posts regarding ASP.Net built in membership functionality,providers,controls. You can read the first one post one here .
So far in all my posts, I have never mentioned anything
about how to implement authentication/authorisation
mechanisms in a web site. In all our professional web
applications we do need some sort of mechanism to verify
who users are and what privileges have in our site.
I was involved in designing and implementing an ASP.Net application some time ago. After we deployed the application we wanted to monitor various aspects of the application.