MSDN Code Gallery

This project contains reference documents regarding SharePoint 2007 topics that I wrote because I couldn't find them in other places.

The DPE demo is a series of client applications including WPF, Silverlight, SharePoint, Word (VSTO) that integrates with the CRM platform. We have a series of developer videos and code samples that helps you get started if you wish to build similar applications.

This kit is meant for developers who are interested in integrating SAP with Office. The OBA Sample Application Kit for SAP includes an installation doc, whitepaper, and source code to help you get up and running with your integration efforts. Specifically, the kit shows you how to integrate SAP (for read/write from and to the SAP system) with Excel 2007, PowerPoint 2007, and Microsoft Office SharePoint Server (MOSS) 2007. Some example technologies demonstrated within the kit are Visual Studio 2008/Visual Studio Tools for Office 3.0, MOSS Business Data Catalog (BDC), Web services.

Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 support a rich security model that allows administrators to control access to sites and content by assigning permissions to users and groups for a specific securable object (such as site, list, library, folder and even an individual document or item). However, in certain scenarios there is a need to secure access to individual columns in lists or document libraries. Currently, SharePoint does not provide out of the box support for securing columns or views. A typical scenario that would require this might be a list that contains a broad spectrum of information about an employee or a client, where certain columns (salary, revenue to date, potential to promote, etc.) might ideally only be viewable by certain groups within the portal. To address those scenarios, this paper describes a method to leverage SharePoint extensibility and built-in item to level security to allow applying column-level permissions to a custom field type. This is accomplished through the use of a lookup field as the column, with behind the scenes ties to another list that contains the secure values and a method to provision those values back to the lookup only for users with valid permissions. The result is that in the view mode authorized users will see the content of a secure column as if it was a normal column, while unauthorized users will not see the content of the column at all. This different behavior is shown in Figure 1. Similarly, only authorized users will be able to access the content of a secure column in new and edit modes.

Expose SharePoint (WSS 3.0) Lists as DataTables! While the default SPList type can return a DataTable (via SPList.Items.GetDataTable), it's disconnected--no databinding--and can't be used to make updates back to the list. Plus, it doesn't have the right schema when it's empty. ListDataTable solves these problems, effectively giving a DataTable bound to the list, respecting Inserts, Updates and Deletes.