Skip to main content

70-562 Intro to profiles


Intro To Profiles

The membership API has it's own databse, and should not be mixed with other data.
The bride with business data like the users credit card or company, maybe the profile can be usefull.

Using a session variable to contain the last visit is not ideal, the variable can be mistyped.
While the Profile.LastVisitedDate; includes this information.

In the system.web, create a profile element and properties element. They will be added with an add element name and type attribute.

After having created those, to access the Profile object from code, it's required to compile first for the web.config to take effect.

The information is stored permanently. By default the data is stored in App_Data\aspnetdb.mdf. To store in a different db, a custom provider needs to be writen.

The App_Data sometimes needs to be refreshed in order to show it's content. Double clicking it opens the server explorer on this db.

You have lots of options, you can use Session, Cache, ViewState and so on for temp data. For persistent data, use Profile.

Profile scalability issue. Loading a property of a profile, will load all the data configured under this provider(lots of data requires lots of providers).

ASP.Net loads all data at once, per provider, so it's important group the data per provider in order to load only the necessary.

In order to use profiles, you have ot configure it in the web.config and use a storage(sql).

allows to add a property, remove, clear will clear all existing properties, group will group related properties.

The attributes for a new property: name, readOnly, serializeAs, provider, defaultValue, type, allowAnonymous.

If the State property is grouped in the Location group, the property would be accessed with Profile.Location.State.

It's possible to use a custom type, a class, and reference it's members as properties in the profile, this calss should be in the App_Code folder.

By default, profile data is stored in App_Data\aspnetdb.mdf, this default is set in the Machine.config and can be copied to the web.config and override them from there.

You can use different providers per properties by specifiying the provider attribute per property.

When creating an account after an anonymous session the information created during the anonymous session is carried into the newly created profile.

You can create a profile based on schema in the web.config, this will allow to get the current profile, check if its anonymous, and call the static Profile.GetProfile mehtod.

Membership and profiles are similar in the sense that you're storing data about the current user in a database.










Comments

Post a Comment

Popular posts from this blog

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

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.
Post a Comment
Read more