February, 2012

The Microsoft Office Developer Center has created 101 code samples for SharePoint 2010. These samples cover a wide range of useful tasks from working with lists and document libraries, to using BCS. The C# samples, in most cases, have a companion VB.NET project. There are also samples written in JavaScript. The list of samples were compiled from suggestions submitted by the SharePoint community via this blog. Be sure to check them out. We are sure that you will find something to use in your own solutions. You can get the descriptions of each sample and a link to each individual sample at: http://code.msdn.microsoft.com/site/search?f%5B0%5D.Type=Topic&f%5B0%5D.Value=Sharepoint%202010%20101%20code%20samples&f%5B0%5D.Text=Sharepoint%202010%20101%20code%20samples The sample pack can be downloaded at: http://code.msdn.microsoft.com/SharePoint-2010-101-Code-da251182 Enjoy!

Summary: See how to retrieve the site collection URL at run time when using a timer job for deployment. In real word scenarios, a common requirement while using timer jobs is to deploy the job in such a way that it runs on only one machine in the farm and retrieves the site collection URL at run time. In this type of situation, it is not recommended that you use a hardcoded URL to compare to the requested site collection URL in the content database or that you use an index to get the URL. To deploy the same solution on different production servers, you would need to modify the deployment code for each individual server which is tedious at best and prone to errors. There are various ways to pass the URL, or any other values, to a timer job. For example, you can use configuration files, external files, property bags such as owstimer.exe.config , XML files, or the property bag for a SharePoint 2010 object. A property bag is simply a container for a series of name/value pairs that correspond...

The figure below is a syntax diagram of the structure of SharePoint Foundation REST service URIs. You can read more about the SharePoint Foundation REST service here . Syntax diagrams are a useful way of illustrating linear data structures. Things like: REST URI composition API signatures JSON, OData, or other XML-based data notation You can find out more about syntax diagrams at this Wikipedia entry , see some examples using JSON here , and see some more examples in the OData specifications .

This post describes how to update ODC files programmatically by using either a SharePoint feature or a console application written in .Net code, or with a PowerShell script. The contents pertain to: Microsoft SharePoint Server 2010 Microsoft SharePoint Server 2010 – Excel Services Microsoft SQL Server 2008 Overview of Office Data Connection Files An Office Data Connection (ODC) file contains connection information about how to connect to a data source and retrieve data for use in various documents such as Microsoft Excel workbooks. Connection information can either be stored in the workbook or in a connection file, such as an (ODC) file (.odc) or a Universal Data Connection (UDC) file (.udcx). Typically, an ODC file is used while building Excel services reports that fetch data from a data source. As part of the implementation, this report can be deployed in multiple environments such as development, staging, test, and production. Each environment may have a different data source and hence...

Today’s diagram is probably best considered a work in progress. We created the following diagram as a prototype, to see if we could use large-scale static graphics as aids for developers to visualize the SharePoint object model hierarchy and the relationships between classes within it. As an experiment, we took the subset of classes available in sandbox solutions, and, starting from a handful of the most important classes, laid out the Microsoft.SharePoint namespace hierarchy. The results were mixed: we quickly realized that, as recursively nested as the SharePoint object model is, arbitrarily picking starting points (even important classes such as SPWeb and SPList) and presenting a single hierarchical view of the object model from there probably isn’t going to be that useful long-term for developers. Locating a specific class was difficult. Also, in order to conserve space, we omitted the names of the members used to access a class from another class; in doing so, we inadvertently stripped...