In addition, we'll review some practical examples regarding how to build end-to-end solutions based on list and library data in Windows Share Point Services.
To understand Share Point lists and libraries from a developer's perspective, we'll dive into the following topics: At the end of this chapter, developers should have a good understanding of both how lists and libraries work in Windows Share Point Services and what developer feature areas and technology components related to lists and libraries can be leveraged in your applications.
This chapter also serves as a technical foundation for later examples related to UI development in Windows Share Point Services, including the creation of new Web Parts and methods to customize list rendering in various Share Point sites.
For a developer, a list is the main mechanism through which data stored in Windows Share Point Services is presented to a user for data input or retrieval.
This means that in many cases customizing a Share Point site requires some customization to the list data or programmatic access to the data from an application that resides outside of Windows Share Point Services.
Before getting started with coding against the Share Point lists and libraries, it's important to understand a little bit more about how lists work, how they're created within the Windows Share Point Services web interface, and what properties they have that can impact how you write code for a list.
To do this, we'll walk through an example involving the creation of a list. As a developer using Share Point lists, you will focus most of your effort on adding, updating, and deleting list items to synchronize your Share Point content with another data store or to serve as a primary store for application data.
by Randy Holloway, Andrej Kyselica, and Steve Caravajal from Wrox Press (ISBN 978-0-470-09740-3, copyright 2008 Wiley Publishing, all rights reserved).