Geeks With Blogs
Tech Notes There are 10 types of people in the world, those who understand binary, and those who dont!

Most Web Parts implementations allow users to create a single portal page where they can personalize the look, feel, functionality, and experience of their "My Home" page in an application. But what if you want to take Web Parts a step further and allow users to define a personalized interface that applies to a series of pages in an application? Wouldn't it be useful if your users could place helpful tools and components on the periphery of your application and have those available on each page they visit instead of just on their "My Home" page? Absolutely! The question is how do you do it?

At first glance, it may seem that Master Pages are the solution to the issue, but you will quickly run into a stumbling block: personalization settings for Web Parts are stored on a page-by-page basis. Even if you define all of the Web Part logic in a single Master Page, the Web Parts personalization settings for the pages that use the Master Page are stored separately from one another, preventing you from applying a single set of Web Parts to every page on the site.

Damon Armstrong explains the solution: To create a personalization provider that stores information from multiple pages into a single data store.

[ Read Now ]

# Damon Armstrong is a technology consultant with Telligent Systems in Dallas, Texas , and author of Pro ASP.NET 2.0 Website Programming

Posted on Thursday, May 18, 2006 2:06 AM | Back to top

Comments on this post: Sharing Web Parts across multiple pages

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Thota Umesh | Powered by: