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.

Web Part Zones<br />

Chapter 4: Windows SharePoint Services Architecture 105<br />

Web Part zones are containers on a Web Part Page that allow a designer to organize<br />

<strong>and</strong> control the behavior of Web Parts. A Web Part zone is part of a system that<br />

allows Web Parts to act differently than typical ASP.NET Server Controls. Placing a<br />

Web Part within a Web Part zone allows the Web Part to take advantage of the architecture<br />

of Window SharePoint Services, while placing a Web Part outside of a Web<br />

Part zone does not.<br />

Static Web Parts<br />

A Web Part zone typically contains one or two Web Parts. However, Web Parts do<br />

not have to be placed into a zone on the Web Part Page. Web Parts that are placed<br />

outside of a Web Part zone are called static Web Parts because they are treated <strong>and</strong><br />

act just like a st<strong>and</strong>ard Web control. A static Web Part <strong>and</strong> its properties are stored<br />

within the Web Part Page (.aspx) file. Because of this, a user cannot interact with a<br />

static Web Part or modify it within a browser.<br />

Dynamic Web Parts<br />

Web Parts that are contained within a Web Part zone are called dynamic Web Parts.<br />

This is because unlike with st<strong>and</strong>ard Web control or static Web Parts, users can modify<br />

the properties of a dynamic Web Part. Web Part zones allow a Web Part to participate<br />

in Windows SharePoint Services by connecting the Web Part to a Windows<br />

SharePoint Services content database. The properties of a dynamic Web Part are<br />

saved to a content database so that users can access the properties <strong>and</strong> manipulate<br />

these properties.<br />

Customization <strong>and</strong> Personalization for Web Parts<br />

The two views of Web Parts that are used in Windows SharePoint Services are<br />

shared or personal. A shared view is a version of the Web Part that is seen by all<br />

users. A personal view is created when a user changes the view to Personal. The<br />

user can then make changes to one or more of the properties of the Web Part that<br />

are only for that user to see. The architecture of a Web Part allows users to save their<br />

changes <strong>and</strong> allows Windows SharePoint Services to keep track of each personal<br />

version of a Web Part.<br />

Customization vs. Personalization<br />

Personalization occurs when a user creates a Personal View of a Web Part, while<br />

customization happens when a user makes a change to a Web Part that affects the<br />

Shared View that is seen by all users. A user must have the rights to design a page

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

Saved successfully!

Ooh no, something went wrong!