List of Figures

Chapter 1: Getting Started

Figure 1-1: A WSS farm provides Web applications.

Figure 1-2: A WSS farm provides Web applications that store their data in content databases.

Figure 1-3: Sites exist within site collections. Each site collection must have a top-level site and can contain a hierarchy of child sites.

Figure 1-4: When creating a new site collection, you are required to specify the name, the target URL, and user account information for one or two site collection administrators.

Figure 1-5: WSS prompts you to select a site template for the top-level site.

Figure 1-6: WSS displays a success message–the new site collection has been created.

Figure 1-7: A new site created from the Blank Site site template

Figure 1-8: Each site provides a Site Settings page that provides various configuration and customization options.

Figure 1-9: The Create Page allows users to provision new site elements on demand.

Figure 1-10: The List Settings command displays a page allowing users to customize a list.

Figure 1-11: Many stock aspects of WSS, such as collaboration lists, are implemented as features.

Figure 1-12: A Visual Studio project for developing a WSS feature

Figure 1-13: Once a feature is installed, it can be activated and deactivated by users.

Figure 1-14: A CustomAction element can be used to add custom menu commands to the site actions menu.

Chapter 2: SharePoint Architecture

Figure 2-1: IIS provides an administration utility to inspect and configure IIS Web sites and virtual directories.

Figure 2-2: IIS uses a device driver named HTTP.SYS to route incoming requests to the proper application pool.

Figure 2-3: A master page defines a common layout and named placeholders that can be replaced within the content pages that link to the master page.

Figure 2-4: The HTTP Request Pipeline allows developers to replace components such as HttpHandler, HttpApplication, and HttpModule.

Figure 2-5: WSS extends the standard ASP.NET HTTP Request Pipeline with its own custom components.

Figure 2-6: WSS employs a custom virtual path provider to employ the .aspx page parser supplied by ASP.NET 2.0.

Figure 2-7: An IIS Web site configured as a Web application has four standard virtual directories including the _layouts directory.

Figure 2-8: The \LAYOUTS directory contains application pages that are accessible from within any site in the farm.

Figure 2-9: A custom application page can easily be programmed against the WSS object model.

Figure 2-10: A menu item created with a CustomAction element makes it easy for the user to navigate to a custom application page.

Figure 2-11: A CustomAction element can add menu items to the ECB menu for items in a list or documents in a document library.

Figure 2-12: An application page can be designed to display information about a specific list item or document.

Chapter 3: Pages and Design

Figure 3-1: A WSS site contains a hierarchy of folders and files. Files such as .aspx and .htm pages can either be in an uncustomized or customized state.

Figure 3-2: The CustomSitePages project demonstrates how to build a feature with custom site page templates.

Figure 3-3: A Module element allows you to provision a site page instance from page templates.

Figure 3-4: Customized pages run in safe mode and cannot contain in-line script.

Figure 3-5: Safe mode processing does not allow controls that are not registered as safe controls.

Figure 3-6: Visual Studio provides a productivity-oriented designer for developing user controls.

Figure 3-7: A Web Part page is designed with one or more Web Part zones.

Chapter 4: Web Parts

Figure 4-1: SharePoint’s implementation of the Web Part framework

Figure 4-2: Even the simplest Web Part renders chrome.

Figure 4-3: The ASP.NET Web Part class model

Figure 4-4: The New Web Parts page enables you to discover Web Parts that have been marked as safe and to add these Web Parts to the Web Part Gallery for the current site collection.

Figure 4-5: After you use a feature to import a Web Part to the Web Part Gallery, a user can add it easily to Web Part pages.

Figure 4-6: Properties defined with the WebBrowsable attribute are exposed automatically in the standard WSS Editor Part.

Figure 4-7: A custom Editor Part permits you to take over the user interface in the task pane that enables users to customize and personalize your persistent Web Part properties.

Figure 4-8: Web Parts support adding custom Verbs to provide extra menu items with either client-side or server-side event handlers.

Figure 4-9: You can establish a connection between two connectable Web Parts while the hosting Web Part page is in Edit Mode.

Figure 4-10: A comparison of the SPLimitedWebPartManager and the SPWebPartManager. For the sake of clarity, not all methods are shown.

Chapter 5: AJAX Web Parts

Figure 5-1: The traditional WSS Web page life cycle

Figure 5-2: The AJAX WSS Web page life cycle

Figure 5-3: The AJAX List View Web Part renders the list’s RSS feed using client-side XSLT.

Chapter 6: Lists and Content Types

Figure 6-1: Each site contains a Site Column Gallery.

Figure 6-2: A user can add columns to a list based on visible custom site column definitions.

Figure 6-3: Custom site column definitions can be added as columns in lists.

Figure 6-4: A custom field type can be used to add a new column to a list.

Figure 6-5: The CompanySize field type in use in a custom list.

Chapter 7: Document Libraries

Figure 7-1: DocumentManager1.aspx contains code to populate an ASP.NET TreeView control with nodes for all documents within the current site.

Figure 7-2: DocumentManager2.aspx demonstrates a programmatic technique for creating new documents through the WSS object model.

Figure 7-3: An ECB menu item can be created for every document.

Figure 7-4: DocumentManager3.aspx uses the WSS object model to inspect document properties.

Figure 7-5: A WSS forms library with a custom form template can serve up InfoPath forms.

Figure 7-6: A .docx file is a ZIP archive known as a package that contains parts and items.

Figure 7-7: Add a reference to the WindowsBase.dll assembly to begin programming against the new packaging API.

Figure 7-8: When you set up the appropriate MIME content type, the user is given a chance to open a server-side–generated .docx file directly in Word.

Figure 7-9: DocumentManager4.aspx demonstrates two ways to generate a .docx file from WSS list data.

Figure 7-10: A package defines a hierarchy of relationships in which the package is always the root.

Figure 7-11: The Package Viewer sample application enables you to inspect the parts within a package.

Figure 7-12: The Developer tab in Word 2007 provides a set of Content Controls.

Figure 7-13: Content Controls can provide user input capabilities to a Word document.

Figure 7-14: The DocumentManager4.aspx custom application page demonstrates the power of using Content Controls together with the XML Data Store to generate formatted Word documents.

Chapter 8: SharePoint Workflows

Figure 8-1: In the WF, programs can model sequential workflows or state machine workflows.

Figure 8-2: WF programs are created by dragging and dropping activities onto the workflow designer.

Figure 8-3: The WSS runtime loads the WF runtime environment and initializes it with a custom runtime service to save and load workflow instances from the content database.

Figure 8-4: WSS provides a standard application page named AddWrkfl.aspx to assist users with the creation of workflow associations.

Figure 8-5: A workflow association can be configured to allow users to launch workflow instances manually.

Figure 8-6: The standard application page named workflow.aspx provides workflow management over items and documents.

Figure 8-7: The Workflow Status page provides information on the status of one specific workflow instance.

Figure 8-8: The Workflow Starter Kit of the WSS SDK provides Visual Studio project templates for creating new custom workflow templates that target WSS.

Figure 8-9: New projects created with the Workflow Starter Kit templates provide a WF program as well as the starting files used to create features.

Figure 8-10: Right-clicking the workflow designer window provides several important context menu items.

Figure 8-11: The properties of activities can be bound to fields within the WF program.

Figure 8-12: Once you successfully deploy and test your Hello World workflow template, you should see your message in the workflow history table for a specific workflow instance.

Figure 8-13: Method activities such as CreateTask perform actions, whereas event activities such as OnTaskCreated respond to actions.

Figure 8-14: Placing an OnTaskChanged activity inside a While activity makes it possible to achieve the correct control-of-flow logic to ensure that a task is properly updated before continuing.

Figure 8-15: You can use the Rule Condition Editor to add a Declarative Rule Condition that controls the looping behavior of a While activity.

Figure 8-16: The LitwareWorkflows project demonstrates how to implement the four different types of workflow input forms.

Figure 8-17: The standard application AddWrkfl.aspx page is always shown before a custom association form.

Figure 8-18: A custom workflow association form is used to gather parameterization information for a new workflow association.

Figure 8-19: The Workflow.aspx page allows users to initiate workflow instances from any available workflow associations.

Figure 8-20: A custom initiation form gives the developer a chance to prompt the user for parameterization data that can be passed to the WF program when the new workflow instance is activated.

Figure 8-21: The WrkStat.aspx workflow status page displays a link for any active workflow modification.

Figure 8-22: A workflow modification form allows users to modify a workflow instance while it is still in progress.

Figure 8-23: You can use an EnableWorkflowModification activity and an OnWorkflowModified activity within the scope of an EventHandlerScopeActivity activity to make a workflow modification active.

Figure 8-24: A custom task edit form allows you to take over the user experience when a user needs to complete a workflow-specific task.

Chapter 9: Solutions and Deployment

Figure 9-1: Folder structure for the Site Definition project

Figure 9-2: Configurations with a Hidden attribute value of false are shown to users as creatable site templates.

Figure 9-3: Visual Studio provides a resource file editor for working with resources, such as literal text strings.

Figure 9-4: Once a solution package is installed, you can manage its deployment through the Solution Management pages of the WSS Central Administration site.