We are happy to announce availability of new SharePoint Client Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint Online. This release again contains few updates on the existing SharePoint CSOM assemblies and some maintenance changes. Main reason for this new release was around the new taxonomy term set capability which is commonly used with term sync tooling cross environments. You can find the latest CSOM package for SharePoint online, including the Project Online CSOM assembly, from the NuGet gallery with an id of ‘Microsoft.SharePointOnline.CSOM’. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. In general we do recommend you to use the Nuget Package to gain access on latest version, rather than downloading the SDK to your machine.

In general we are looking into moving to monthly cadence around CSOM Nuget updates with locked and consistent release dates. This process should be fully in place during autumn 2016. 

Version of the newly released CSOM package is 16.1.5326.1200. Previous versions of the NuGet has not been removed, so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the Nuget version is increased to 16.1.5326.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which alings with the Nuget version.

Notice. If you like to operate with SharePoint Online rather using PowerShell, we are also looking to update the SharePoint Online Management Shell during upcoming days. Documentation for SharePoint Online Management Shell will be updated accordingly based on the changes in latest version.

New properties and methods cross assemblies

Here’s a raw list of all the new properties and methods in the assemblies. This is relatively short list this time, since previous version was just released few weeks back. Notice that you can keep on using older version as well, unless you want to have access on any of the new APIs released now. 

Microsoft.SharePoint.Client

• public property Microsoft.SharePoint.Client.ChangeItem.ActivityType
• public property Microsoft.SharePoint.Client.ChangeItem.Hashtag
• public property Microsoft.SharePoint.Client.ChangeItem.ListTitle
• public property Microsoft.SharePoint.Client.ChangeQuery.Activity
• public property Microsoft.SharePoint.Client.File.ServerRelativePath
• public property Microsoft.SharePoint.Client.Folder.ServerRelativePath
• public property Microsoft.SharePoint.Client.Hashtag.Application
• public class Microsoft.SharePoint.Client.ResourcePath
• public property Microsoft.SharePoint.Client.Site.ServerRelativePath
• public method Microsoft.SharePoint.Client.Web.GetFileByServerRelativePath
• public property Microsoft.SharePoint.Client.Web.ServerRelativePath

Notice that there’s a small breaking change in the following method. Propability of this method being in use is really small and you’ll see the change when you’ll be compiling your code agains the latest version. In general we are trying to minimize these kind of breaking changes as much as possible, but ever now and then they might be required. 

• public method Microsoft.SharePoint.Client.List.CreateDocumentAndGetEditLink – string templateUrl added as method parameter

Microsoft.SharePoint.Client.Taxonomy

• public method Microsoft.SharePoint.Client.Taxonomy.TermSet.GetAllTermsIncludeDeprecated

Microsoft.ProjectServer.Client

• public property Microsoft.ProjectServer.Client.DraftTask
• public property Microsoft.ProjectServer.Client.PublishedTask.StatusManager
• public property Microsoft.ProjectServer.Client.StatusTask.StatusManager
• public property Microsoft.ProjectServer.Client.TaskCreationInformation.StatusManager

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, Office 365, Microsoft – 9th of June 2016