Skip to main content

70-562 Membership API




Membership class: Provides the api to manage users, create, find, generatePassword, ValidateUser, and more...

MembershipUser Class: Stores name, email, password, question/answer, but doesnt manager user defined properties like profiles GetPassword, ResetPassword, UpdateUser, properties describing user info. One could make a page that allows to find users, delete user, select user from a listView control, which would provide a details view and update a password, or button to reset it.

Managing users from your own interface instead of configuration manager or web.config

API: MembershpiCreateStatus, Membership.Createuser(...), Membership.GetallAllUsers() retunrs an array of users. Membership.DeleteUser(strUserName), MembershipUser user = Membership.GetUser(strUserName), user.ChangePassword(old, new),
user.ChangePaswwrdQuestionAndAnswer(...), Membership.FindUsersByEmail(strUserName), Membership.FindUserByName(strUserName), user.ResetPassword(oldPassword), Managing Roles from your own interface instead of configuration manager or web.config

Roles Class: AddUser(s)ToRole(s)(...), CreateRole/DeleteRole, GetUsersInRole retrieves MembershipUsers objects, FindUsersInRole returns juste the names, GetRolesForUser/IsUserInRole, GetAllRoles returns a list of roles, RemoveUser(s)FromRole(s), RoleExists(s).

The delete from role method will delete user(s) from the role, and there is also another method that deletes the role itself or throws an exception if there is a user in this role.

Creating a custom provider

Membership and roles layer are based on the provider concept, that, API abstracted from data acesss layer. To create a provider that doesnt use sql server or express, you'd add a class to the App_Code folder. Inherti fromSystem.Web.Security.MembershipProvider or RoleProvider, Provide all the code for each of the methods, they map one to one to the API and you need to supply them all if you're creating your own provider. When inherting from the provider, let visual studio create the member stubs by right clicking on the class you inherit from, it will insert all the mothods you need to implement.

Membership controls vs custom providers

The controls have a property that indicates wich provider to use. You can also create your own controls and use the

Membership and roles API.



Comments

Post a Comment

Popular posts from this blog

70-562 ListView

List View is a versatile control that allows to work with a signle control rather than many smaller controls. Provides rich sorting, deleting, editing, it is one of the most flexible grid control. Design view can fill the ListView with fake data to give an overview. In designer, the configure list view link might not show, (currently a bug), to fix configure the datasource but cancel then click configure datasource again and this time click finish and the Cofnoigure ListView link will show up in the smarttag. You can choose templates, LayoutTemplate is crucial, ItemTemplate(a row is part of a table, in a list view they are called items since they don't have to correspond to a table row), AlternatingItemTemplate, ItemSeparatorTemplate, SelectedItem, EmptyItemTemplate, EditItemTemplate, InsertItemTemplate allows to customize what the user will be presented when creating an item, EmptyDataTemplate. The itemPlaceHolder and the groupPlaceHolder are important elements as the will b...
Post a Comment
Read more

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

70-562 Tracing

Tracing can be enabled from the page directive, programmatically or from the web.config. This will append the trace info to the bottom of the page. There several tables of grouped trace information: Life cycle events, controls used by page, sessions state, cookies, http reuqest headers, server variables. SessionID, Time spent in each event, and check that the events are executing in the expected order. The control tree give a hierarchy of the controls in the page, and how much the control is using in the viewstate, and render by tells how much room the control uses on the page. See cookie information. And can see the Header information incase you do any kind of header manipulation. Also see query string collection. Also see the server variables passed back and forth between the server and the client application, logon user, remote user. Enable tracing when not in production, (remember to disable it when building a release... that and the debug= true setting get forg...
Post a Comment
Read more