Skip to main content

70-562 Anonymous Profiles

 Anonymous profiles

How does asp.net track anonymous users and store their profiles?

Setting anonymousIdentification to true in the web.config, asp.net stores a guid for each anonymous user, allowing concurent anymous users to log in, and those should be cleaned in your databse every once in a while.

For each property that is available to anonymous user, the allowAnonymous must be set to true.

How to carry the information of a anonymous user when he carries a new profile.

The magic happens in the global.asax, and create an event handler, Profile_MigrateAnonymous, by getting the anonymous id from it's event args, get the profile with this id, we check one of properties to make sure we dont overwrite an existing profile.

To store in other than SQL you need to create a custom profile provider that inherits from System.Web.Profile.ProfileProvider. For example an xml file could be used to store.

There is a provider toolkit availble on microsoft sites that makes creating custom providers easier.

Session vs Profiles,

Session uses strings for each value, and requires to know the datatype to be cast, and is just stored for the current session.

Profile provides intellisense and strong typing and retrieves the data only once when request, stores when is persisted.

Profiles can be used to store user preferences, and web parts can benifit for the persistence mecanisms of profiles.

Comments

Popular posts from this blog

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.

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.

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.