List of Listings

Chapter 2: SharePoint Architecture

Listing 2-1: A custom application page can contain HTML layout and in-line code.

Listing 2-2: A custom application page can reference a code-behind base class.

Listing 2-3: A code-behind class for an application page should inherit from LayoutsPageBase.

Chapter 4: Web Parts

Listing 4-1: A very simple Web Part

Listing 4-2: The first steps in Web Part development

Listing 4-3: An example Web Part description file

Listing 4-4: A custom Editor Part for updating RssViewWebPart property values

Listing 4-5: An Asynchronous RSS Web Part using Page.RegisterAsyncTask

Listing 4-6: A simple XSLT resource for transforming RSS XML

Listing 4-13: A utility class for resource access

Listing 4-7: An example Web Part that loads a User Control

Listing 4-8: A feed list Web Part using the SPGridView control

Listing 4-9: An example Web Part Verb implementation

Listing 4-10: Example connection provider and consumer Web Parts

Listing 4-11: Converting the Feed List Web Part to an IFieldProvider

Listing 4-12: Enabling a connection to an IFieldProvider

Listing 4-14: Manipulating Web Parts using SharePoint’s site model

Listing 4-15: Exporting Web Parts using SharePoint’s site model

Chapter 5: AJAX Web Parts

Listing 5-1: EditableControl.js-a simple component for an editable AJAX control

Listing 5-2: AJAX-enabled Web services are marked with the ScriptService attribute.

Listing 5-3: The WikiControl uses script-enabled Web services for persistence.

Listing 5-4: The WikiWebService with WSS list backing demonstrates a flexible API for WSS AJAX components.

Listing 5-5: The Feed List Handler provides an outline of XML feeds for the site.

Listing 5-6: The MicroWiki WebPart demonstrates a simple AJAX implementation.

Listing 5-7: The SharePoint.Ajax.XmlComponent demonstrates an AJAX component for client-side XML loading and transforms.

Listing 5-8: The AjaxWebPart provides a common base class for AJAX Web Parts.

Listing 5-9: The Feed List Web Part implements the XmlWebPart.

Listing 5-10: The OPML XSLT defines the user interface for the AJAX component.

Listing 5-11: The AJAX List View Web Part accepts connections from the AJAX Feed List Web Part.

Chapter 6: Lists and Content Types

Listing 6-1: Creating a new list instance using the WSS object model

Listing 6-2: The site data query applied to recently published Items

Listing 6-3: The standard FirstName site column definition

Listing 6-4: The LitwareTypes feature is scoped at the site collection level.

Listing 6-5: An example of creating custom column definitions

Listing 6-6: A custom field type is created by creating a class that inherits from SPFieldText or one of the other built-in field type classes.

Listing 6-7: Code to initialize the field control for the CompanySize field type

Listing 6-8: Implementing a custom field type requires writing a field schema using CAML.

Listing 6-9: A site column feature manifest for a custom field type

Listing 6-10: The Company content type defines an ID and a Name along with a collection of site columns.

Listing 6-11: The skeleton of the schema.xml file for the VendorList type

Listing 6-12: The list schema within the schema.xml file defines a Fields collection.

Listing 6-13: An announcements RSS feed, autogenerated by Windows SharePoint Services

Listing 6-14: An example list event receiver

Listing 6-15: You can use a feature to bind event handlers to a specific list type.

Listing 6-16: Event handlers can be bound to list events through the WSS object model.

Listing 6-17: An example of how to structure event validation logic

Listing 6-18: Event handlers for after events can be used to maintain data integrity.

Listing 6-19: An XmlDocument element can be used to bind an event handler to a content type.

Chapter 9: Solutions and Deployment

Listing 9-1: The basic Site Definition project schema

Listing 9-2: A .ddf file defining the solution structure

Listing 9-3: Solution package manifest for the Litware Types solution

Listing 9-4: Web Config Modification Console demonstrates simple use of SPWebApplication and SPWebConfigModification.

Listing 9-5: The US English language pack CAB definition

Listing 9-6: The US English language pack solution manifest

Listing 9-7: The Japanese language pack CAB definition

Listing 9-8: The Japanese language pack solution manifest

Listing 9-9: The final Litware Web Parts build script

Listing 9-10: The Japanese site definition language pack CAB definition

Listing 9-11: The Japanese site definition language pack solution manifest

Listing 9-12: Final build script for the Litware site definition

Chapter 10: Application Security

Listing 10-1: The example SecurityWebPart class demonstrates CAS security policies.

Listing 10-2: Security policy in the solution manifest

Listing 10-3: The Elevated Privilege Web Part demonstrates the security context of the SPSite object.

Listing 10-4: The Visitor Tracker Web Part demonstrates the RunWithElevatedPrivileges security method.

Listing 10-5: The ISecurableObject interface

Listing 10-6: The SPBasePermission enumeration