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.

820 Part IX: Maintaining a Server in Windows SharePoint Services<br />

■ Web Parts that can be used on portal <strong>and</strong> Windows SharePoint Services websites;<br />

for example:<br />

■ Content Editor Web Part: Displays unstructured Web content, such as text<br />

or images.<br />

■ Form Web Part: Allows you to add an HTML form.<br />

■ Image Web Part: Displays a picture.<br />

These <strong>and</strong> other built-in Web Parts will be explained later in this chapter.<br />

SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> are built on top of the <strong>Microsoft</strong> .NET<br />

Framework 1.1, <strong>and</strong> Web Parts are therefore <strong>Microsoft</strong> ASP.NET Web Form custom<br />

server controls. Web Part Pages include a number of zones, where each zone can<br />

contain a number of Web Parts. Web Part Page Zones are detailed in Chapter 30,<br />

“Default Tools to Customize Windows SharePoint Services.” Web Parts can also be<br />

placed directly on a Web Part Page—that is, outside a Web Part Page Zone—by Page<br />

Authors at design time, <strong>and</strong> therefore the layout <strong>and</strong> properties of these Web Parts<br />

are fixed by the designer of the Web Part. They cannot be minimized or closed, nor<br />

can their properties be modified in the browser. Such Web Parts are called static<br />

Web Parts. A static Web Part <strong>and</strong> its properties are stored in the Web Part Page (the<br />

.aspx file), not in the SQL content database for the site.<br />

Dynamic Web Parts are Web Parts that are contained in a Web Part Page<br />

Zone <strong>and</strong> can be customized by using the browser. Users with the right to Add/<br />

Remove Private Web Parts or to Add And Customize Pages can, using the browser,<br />

add a dynamic Web Part into any zone on most Web Part Pages, on any site that is<br />

a SharePoint Portal Server site, or on any site that is based on Windows SharePoint<br />

Services. Even if a Web Part Page contains Web Part Page Zones, this does not imply<br />

that a Web Part can always be added to the Web Part Page. One example of a Web<br />

Part Page to which you cannot add a Web Part by using the browser is any Web Part<br />

Page that is based on the Site Directory area template. This, together with zones <strong>and</strong><br />

security rights for Web Parts, was discussed in Chapter 30. You can add dynamic<br />

Web Parts to pages by dragging <strong>and</strong> dropping them in a browser, as described in<br />

Chapter 23, “Personalization Services in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>,” <strong>and</strong><br />

in Chapter 30.<br />

Basic Customization of Dynamic Web Parts<br />

A dynamic Web Part is stored in the content database rather than in the Web Part<br />

Page (the .aspx file); therefore, changes do not affect the underlying .aspx page.<br />

Once a Web Part is added to a Web Part Page, you can customize it by setting properties.<br />

When you set Web Part properties in the browser, the scope of the modifica-

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

Saved successfully!

Ooh no, something went wrong!