September, 2011

Item scheduling is a special facility in SharePoint 2010 which helps to publish a document/page for a specified period. This feature is available out-of-the-box for publishing sites for the Pages library. It can also be implemented in a Team Site for custom document libraries. The following sections describe how to set-up item scheduling. Activate Publishing Timer Job Definitions for the Web Application’s Document Library Perform the following steps in Central Administration: On the Quick Launch menu, select Monitoring . In the Timer Jobs section, click Review Job Definitions . In the screen, ensure that the highlighted jobs are shown with the specified Web application. Click Scheduled Approval . In the screen, ensure that the Disable button is visible. This indicates that the job is enabled for the Web application. Set a schedule for the job to run; for example, every 5 minutes. Click Scheduled Unpublish and ensure that it is enabled and that an execution...

In this fourth article of our SharePoint Continuous Integration series, we will look at how to implement assembly versioning as part of a Team Foundation Server (TFS) build. Versioning refers to changing the version number or name with each new release of code. Versioning is important because it enables you to easily see which version of a piece of code is installed in a particular environment. On the .NET platform, the version is typically represented as a four-part number, starting with 1.0.0.0 by default, that exists on each .NET assembly. Incrementing the version can be done manually, but where an automated build process exists (such as in a nightly build), it’s beneficial and a common practice to make versioning an automated step. Note that in TFS 2010, there is no simple configuration switch to enable versioning; some customization of the build process is required. This post provides a step-by-step guide for customizing the build process. Although assembly versioning is a...

The following diagram shows the call and response flow for the client object models in SharePoint Online. SharePoint Online includes three client object models. The ECMAScript, .NET Framework managed, and Silverlight client object models each include objects that correspond to major objects at the site-collection level or lower in the SharePoint hierarchy. The object models provide a consistent and easy-to-use, object-oriented system for interoperating with SharePoint data from a remote client or server. Because code written against the client object models runs remotely on the client, it is not subject to the same restrictions as sandboxed solutions, and can, for example, access external data sources. The client object models are provided through proxy .js files and managed .dll files, which can be referenced in custom applications just as other object models. All operations are inherently asynchronous, and commands are serialized into XML and sent to the server in a single HTTP request...

When you configure a SharePoint 2010 web application in claims mode, different authentication options are available. These options determine the flow of the authentication process. To learn more about authentication options, see Authorization and Authentication . The following figure shows the steps in the authentication process. It explains, in order, the different routes that the authentication process flow can have, based on the authentication options that are available in SharePoint 2010. Steps in the Authentication Process The client requests a SharePoint resource. As part of the request pipeline, if the request is not authenticated, the authentication components route the request based on the authentication settings for that zone. The request is then processed by the authentication components. When more than one authentication method is configured for the given zone, the authentication selection page enables the user to choose the authentication method. If only one authentication...

The offline Help for the SharePoint 2010 SDK has been updated, and there are several technical articles now available. Happy reading! SDK Content · Updated : SharePoint 2010 SDK content for local (offline) Visual Studio 2010 Help Library (In Visual Studio, Help | Manage Help Settings | Check for updates online) Technical Articles · Claims Architecture and Scenarios for SharePoint 2010 Developers Provided by: Siew Moi Khor | Editor: Kimberly Hope · Customizing SharePoint Online with SharePoint Designer 2010 Provided by: Asif Rehmani | Dail Magee Jr. Beck Andros

The following diagram shows the basic steps in the process of creating, deploying, and activating a sandboxed solution on SharePoint Online: 1. Develop and test the solution. To create or customize SharePoint Online solutions, you must develop the solution on a local computer where SharePoint Server 2010 or SharePoint Foundation 2010 is installed. This includes debugging the solution; you will not be able to debug the solution directly on SharePoint Online. After you set up your development environment, you can use Visual Studio 2010 to create your sandboxed solutions. In addition, Visual Studio 2010 can open and edit solution package (.wsp) files that are created in SharePoint Designer 2010, enabling designers and developers to tightly collaborate on solutions through a common framework. 2. Deploy and activate the solution. After you create and debug your sandboxed solutions on your local computer, you must hand that solution off to your SharePoint Online administrator, if you do not have...