A start-to-finish mini-application that illustrates how and why you might implement a provider-based solution in a Windows Forms application.

So how do you programmatically determine if a provider is getting its configuration from the default (machine.config) file or from an application-specific (web.config) file?

The Asp.net membership provider was designed to allow for self-service password management but through an understanding of the configuration options as well as a combined use certain provider methods, web site administrators can effectively manage member passwords.

Implement the Provider Model in your own applications for cleaner implementations, increased revenues and increased customer satisfaction

Understanding the role of the ApplicationID column in the Asp.Net membership tables and how the various membership providers map to this ID through the ApplicationName attribute in web.config.