You want to use ASP.NET 2.0’s profile features but you do not want to define the profile information in the web.config file because you use the same profile definition in multiple applications.
Implement the membership features to provide user authentication, as described in Recipe 9.5, create a custom class that inherits from
ProfileBase, add properties for each user-specific data item you want to include in the profile, and modify the
<profile> element in web.config to set the
inherits attribute to the custom class you created to store the user’s profile data.
Use the .NET language of your choice to create a custom class for the profile data:
Add a property for each data item to be included in the user profile
Modify web.config as follows:
<profile> element with a
<provider> element defining the provider used to store and retrieve user-specific data.
inherits attribute of the
<profile> element to the fully qualified namespace of the custom class you created.
Example 10-5 shows the modifications made to web.config for this solution. The custom user profile class is shown in Examples 10-6 (VB) and 10-7 (C#). The example page that uses the user profile information is identical to the example in Recipe 10.1 and is shown in Examples 10-2, 10-3 through 10-4.
If you use the same user profile data in multiple applications, defining the profile in web.config creates a maintenance problem when any changes ...