Posted by : Rhyf Ahmad Wednesday, May 13, 2015

The ASP.NET provider model is an important framework to understand as you build your applications. The ASP.NET provider model was a major change introduced back with the release of ASP.NET 2.0, so you probably already know that ASP.NET is a way to build applications for the Internet. For the Internet means that an application ’ s display code travels over HTTP, which is a stateless protocol. ASP.NET works with a disconnected architecture.
The simple nature of this model means that requests come in and then responses are sent back. On top of that, ASP.NET does not differentiate one request from another. The server containing an ASP.NET application is simply reacting to any request thrown at it. This means that a developer building a Web application has to put some thought into how users can remain in context between their requests to the server as they work through the application. Keeping a user in context means recording state, the state of the user, to some type of data store. This can be done in multiple ways, and no one way is the perfect way. Rather, you must choose one of the available methods.


Understanding the Provider
The Provider Model in ASP.NET 4
  1. Setting Up Your Provider to Work with Microsoft SQL Server 7.0, 2000, 2005, or 2008
  2. Membership Providers
  3. Role Providers
  4. The Personalization Provider
  5. The SiteMap Provider
  6. SessionState Providers
  7. Web Event Providers
  8. Configuration Providers
  9. The Web Parts Provider

Configuring Providers 

Ebook Preview
Get the ebook now (897 kB)

If the link above doesn't work, try the link below

Mirror: Get the ebook now (897 kB)

Leave a Reply

You can leave a comment to request any article(s), software(s), ebook(s) or report the dead link.
Then I will reply as soon as I can :)

Subscribe to Posts | Subscribe to Comments

Welcome to My Blog

Recent Post

Recent Posts Widget

- Copyright © Madriva -Robotic Notes- Powered by Blogger - Designed by Johanes Djogan -