Rjs web webcontrol popcalendar12/20/2023 ![]() ![]() The above can be better understood by having a look at the Membership API class hierarchy (Figure 1). In addition, the MembershipUser class discussed above represents a single member in the Membership API database. The Membership class contains a set of static methods that provide the entire functionality of the Membership API to the user-interface layer in any Web application. The SqlMembershipProvider and ActiveDirectoryMembershipProvider represent a concrete implementation of the MembershipProvider class. The Membership API provider model consists of the MembershipProvider, which inherits from the ProviderBase, which is the base provider for all the new provider-based features in ASP.NET 2.0. This article will focus mainly on extending the default database that ships with the new database-related features in ASP.NET 2.0 so that you can store additional related information about a member in the Web application. You can choose a number of ways to overcome the limitation of the MembershipUser properties in ASP.NET 2.0’s Membership API. This last issue is not mainly a limitation just because Microsoft built the Membership API upon the provider model-another provider can easily replace the model with any database implementation available. In addition to the Membership API’s need for more properties, it has another important limitation-by default it only works with Microsoft SQL Server and Active Directory. ![]() Usually, in middle to large-scale applications, a member’s record requires the presence of a lot more properties and those properties are not all currently found in the MembershipUser class.Īlthough the Membership API presents a generic member’s record, Microsoft built the Membership API upon the provider model, so, you can easily solve that limitation and extend the current Membership API to serve your needs. This class does not support the First Name and Last Name properties, for example. For example, the MembershipUser class, which is found in the Membership API and represents a member saved in the application’s database, contains a limited number of properties. But a problem arises when working with huge applications. The Membership API works fine with small Web applications. I will not spend more time on the Membership API controls in this article-you can find many online resources and articles to get more information. You would end up creating a User control or a Server control so you would not need to repeat your work again and again.ĪSP.NET 2.0 provides a Role Management API that works with the Membership API to provide a full solution for the authentication and authorization needed for most Web applications you develop. In ASP.NET 1.x, you had to add this control to each application you developed. This control contains the username and password fields used to authenticate every user who tries to access a secure area inside the Web application. The Membership API provides many ready-made features that you had always needed to build in ASP.NET 1.x and that took hundreds of lines of code to accomplish.įor example, the Membership API has the Login control. NET Framework and you can access all its objects and methods from one namespace reference,. As with the other new features in ASP.NET 2.0, Microsoft integrated the Membership API into the. Microsoft built their Membership API upon the provider model. Microsoft ASP.NET 2.0 provides many new features, such as the Membership API, where you no longer need to worry about membership management in any application you develop. You would usually end up creating your own membership API to be able to use in any application you were working on. ![]() In the days of ASP.NET 1.x, managing an application’s members and roles was a hectic job, especially when most of the middle and higher-level applications needed that kind of management. This article discusses one of the techniques that you can use to overcome this limitation and extend the Microsoft ASP.NET 2.0 Membership API to accommodate custom member records with a solution that works on top of the Membership API without requiring any change in the API. To have a better understanding of the provider model in ASP.NET 2.0, I highly recommend the following link: Provider Model in Depth ( ) However, this API best suits small to medium Web sites due to their limitation in expressing a detailed member record. Microsoft ASP.NET 2.0 shipped with a complete membership API that allows developers to manage the application’s users and their roles. In this article, I’ll present one of the available techniques used to extend the Microsoft ASP.NET 2.0 Membership API to solve some of the limitations of that API. Working with big applications requires extending the Microsoft ASP.NET 2.0 Membership API to handle more detailed member records. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |