Why profile in asp.net

Sky Sanders Sky Sanders Add this namespace in your page System. Profile using System. Profile; i use it. But resulst is the same. Ram kiran Pachigolla Juan Felipe Juan Felipe 1. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. The dynamically created profile class is named ProfileCommon and derives from ProfileBase. All ASP. NET applications have a Profile object, but each application will be bound to a distinct profile object.

All profile classes, though, share a certain behaviour — the behaviour provided by the parent ProfileBase class. This class provides methods to retrieve and update the profile and manage the persistence of the user profile.

An instance of the profile object is associated with each authenticated user that happens to use the application. As the user interacts with the application, the profile may be updated. At the end of each request, the state of the profile is persisted to the data store.

When a new request comes in from the same user, the profile is retrieved from the data store and attached to the context of the request. This behaviour is built into the ProfileBase class.

The ASP. The overall functionality is not surprising per se. In ASP. NET runtime, and to save and read the profile of a given user. Any personalization data is persisted on a per-user basis and is permanently stored until someone with administrative privileges deletes it. The data storage is hidden from the user and, to some extent, from the programmer.

Then, the personalization provider determines the data store to use. Figure 1 provides a graphical view of the role played by the profile provider. The profile module kicks in once the request has been authenticated. Using the identity of the user as a key, the module interrogates the registered profile provider to get the profile object for the current user.

The HTTP context object associated with the pending request initially exposes an empty instance of the ProfileCommon class with the application-specific layout — the HttpContext.

Profile property. Next, the provider stores any information in the profile property on the HttpContext object. From now on, the code attached to the page can consume this data using the Profile member on the HttpContext class. Any property registered through the web. The ProfileCommon class, as defined by the development team, is definitely part of the project and can be accessed directly and without intermediate filters. When the request is going to terminate, the profile HTTP module kicks in again and orders the profile provider to serialize the status of the profile object for the current user.

The name and type attributes are common to all types of providers and indicate the name and class information for the specified provider. The description attribute gives the expected behaviour of the provider, and the connectionStringName contains the information needed to set up a connection with the data store. A custom profile provider is a class that inherits from the base class ProfileProvider and overrides a handful of methods.

The default provider stores profile information to the aspnetdb. NET NET application and has a fixed set of tables and schema. Note that the same database contains tables to hold membership and roles information. You then deploy the database to the production machine as part of the application setup. Inside the profile data model When defining the profile data model in the web. The profile data model is the set of properties you want to define on the dynamically created ProfileCommon class.

Note that Name and Type are the only mandatory attributes. Table 1: Attributes for the profile data model Attribute Description Name Specifies the name of the property. Type Specifies the type of the property. AllowAnonymous Indicates whether the property is usable by anonymous users. DefaultValue Specifies the default value for the property. Web sites are designed for repeated visits from the users.

Personalization allows a site to remember the user identity and other information details, and it presents an individualistic environment to each user. NET provides services for personalizing a web site to suit a particular client's taste and preference.

NET personalization service is based on user profile. User profile defines the kind of information about the user that the site needs. For example, name, age, address, date of birth, and phone number. This information is defined in the web. Profiling ASP. The manner in which you profile your application depends on the development tool that you use to create the ASP. NET application. Any ASP. NET applications. The following topics provide instructions on different ways to profile ASP.

NET Development Server. This sample demonstrates how to work with two linked tables.