16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

106 Part II: SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> Architecture<br />

in order to change the Shared View of a page. By default, Windows SharePoint Services<br />

displays pages in Shared View. Once a user switches to a Personal View of the<br />

page <strong>and</strong> makes a change, the page defaults to Personal View when displayed. A<br />

Web Part page can be designed to default to Personal View if the meta tag Web-<br />

PartPage DefaultviewPersonal is included in the .aspx code.<br />

Personalization<br />

Once a user switches to the Personal View of a page, personalization is as simple as<br />

adjusting a property in the display of a Web Part on a site page. It can also include<br />

adding a Web Part to a page. The added Web Part can be viewed only by the user<br />

who personalized the Web Part. The properties of a dynamic Web Part are stored in<br />

a Windows SharePoint Services content database. Once a user makes a change to a<br />

property, that change is stored as a personal version of the Web Part. Only properties<br />

that are changed from Shared View are stored separately in the database. Windows<br />

SharePoint Services reconciles the differences <strong>and</strong> applies the properties for<br />

the Personal View when the Web Part is rendered for that user.<br />

Controlling Personalization<br />

Web Part zones can be used to control whether a Web Part’s properties can be<br />

changed. By manipulating the properties of a Web Part zone, a designer can choose<br />

to disallow modifications to the Web Parts contained in the zone. They can even<br />

choose to allow customization for a Shared View but disallow personalization in<br />

Personal View. The properties of a Web Part zone cannot be modified through a<br />

browser; they can be modified only with an HTML editor that works with Windows<br />

SharePoint Services.<br />

Regardless of the number of times the properties of a Web Part are modified,<br />

the code in the assembly file never needs to change. All the different versions of a<br />

Web Part reference <strong>and</strong> use the same assembly file.<br />

Exporting Web Parts<br />

Web Parts are designed so that they can be easily shared among users. A user can<br />

export a Personal View or a Shared View of a Web Part by selecting the Export comm<strong>and</strong><br />

from the Web Part menu. When this comm<strong>and</strong> is selected, the entire Web Part<br />

is not actually exported. Instead, only the properties of the Web Part are exported.<br />

When a Web Part is installed, the properties are contained in a description file<br />

that has a .dwp extension. A user creates a new version of a description file by<br />

exporting a Web Part. When the Export comm<strong>and</strong> is selected from the Web Part<br />

menu, the current state of the properties are read from the content database <strong>and</strong><br />

saved to a description file.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!