(Phil Harding) In part 1 we created an InfoPath form which used the SharePoint Object Model to create a new Task list item in a SharePoint site.

These white papers describe the performance and capacity impact of specific feature sets included in Microsoft SharePoint Server 2010.

(Jim McCoy) With SharePoint Workspace 2010, you can access file data housed in SharePoint Workspace through Windows Explorer and certain Office applications. This is true for both SharePoint workspaces and Groove workspaces, though Groove workspaces must be 2010 workspaces.

(Frank Rice) The SharePoint 2010 client object model provides a unified and complete object model for Microsoft SharePoint 2010 developers to access SharePoint site data from remote clients. In this exercise, you use the new SharePoint 2010 client object model and create a Windows Presentation Found

(Tajeshwar Singh) Microsoft Business Connectivity Services (BCS) is the new version of Microsoft Office SharePoint Server 2007 Business Data Catalog functionality. New features are added that help retrieve binary large object data (referred to as BLOB data) from external systems and make it availabl

(Joseph Krupinski) I know I haven’t written for quite some time and I am apologetic for that, however, this post hopefully will make up for it.

(Jim Roth) How to use a SharePoint list as a datasource to an InfoPath form. This is performed using code-behind in the InfoPath form, using Visual Studio Tools for Applications (VSTA).

(Mark Arend) SharePoint 2010 uses two services related to session state that have similar names but are separate and have different purposes.

(Mark Arend) This is an overview of major tools and techniques available to monitor the health of your SharePoint 2010 farm.

(Russ Maxwell) This blog is intended to fill some gaps and provide a foundation to understand components in the claims model and how these components work together. Claims will provide a huge benefit which I will outline some of those benefits below.