{"id":642,"date":"2016-11-24T00:00:00","date_gmt":"2016-11-24T00:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=642"},"modified":"2021-11-15T11:01:38","modified_gmt":"2021-11-15T19:01:38","slug":"new-sharepoint-csom-version-released-for-office-365-november-2016","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/new-sharepoint-csom-version-released-for-office-365-november-2016\/","title":{"rendered":"New SharePoint CSOM version released for SharePoint Online &#8211; November 2016"},"content":{"rendered":"<div id=\"body-content\">\n<p>We are happy to announce availability of new&nbsp;SharePoint Client Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release again contains&nbsp;few updates on the existing SharePoint CSOM assemblies and some maintenance changes. These monthly changes are not significant, but we want to align on the monthly rhythm in future, so that you can&nbsp;know beforehand that there will be new version arriving during end of each month.&nbsp;<\/p>\n<p>You can find the latest CSOM package for SharePoint Online, including the Project Online CSOM assembly, from the <a href=\"https:\/\/www.nuget.org\/packages\/Microsoft.SharePointOnline.CSOM\">NuGet gallery<\/a> with an id of &#8216;<em>Microsoft.SharePointOnline.CSOM<\/em>&#8216;. 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. We do recommend you to use the NuGet Package to gain access on latest version, rather than downloading&nbsp;the SDK to your machine.<\/p>\n<p>Version of the newly released CSOM package is <strong>16.1.5903.1200<\/strong>. Previous&nbsp;versions of the NuGet has <strong>not<\/strong> been removed, so that your existing solutions will continue working without issues and you can decide when the new version is taken into use.&nbsp;Notice that even though the Nuget version is increased to 16.1.5903.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the <em>File Version attribute<\/em>, which aligns with the NuGet version.<\/p>\n<p><img decoding=\"async\" class=\"img-responsive\" width=\"1000\" height=\"578\" alt=\"Picture of SharePoint Online CSOM NuGet package from NuGet Gallery with version 16.1.5903.1200\" src=\"https:\/\/officedevblogs.wpengine.com\/wp-content\/uploads\/2018\/05\/SPCSOMNuget16159031200.png\"><\/p>\n<p><strong><em>Notice<\/em><\/strong>&nbsp;that since this NuGet&nbsp;package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and&nbsp;dependency to your target environment is clarified in following blog post &#8211; <a href=\"http:\/\/officedevblogs.wpengine.com\/using-correct-csom-version-for-sharepoint-customizations\">Using correct Client Side Object Model (CSOM) version for SharePoint customizations<\/a>.&nbsp;We have released separate NuGet packages for on-premises. See following blog post for additional details &#8211; <a href=\"https:\/\/officedevblogs.wpengine.com\/sharepoint-csom-versions-for-on-premises-released-as-nuget-packages\">SharePoint CSOM versions for on-premises released as NuGet packages<\/a>.<\/p>\n<p><h2>New properties and methods cross assemblies<\/h2>\n<p>Here&#8217;s a raw list of all the changes in the classes,&nbsp;properties and methods within this package.&nbsp;<\/p>\n<h2>Microsoft.SharePoint.Client<\/h2>\n<p>Following property has been <strong>removed<\/strong>.<\/p>\n<ul>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.AttachmentCreationInformationUsingPathl<\/li>\n<\/ul>\n<p>Following properties, classes and methods have been <strong>added.<\/strong><\/p>\n<ul>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Field.NoCrawl<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Field.Sealed &#8211; <em>Set<\/em>&nbsp;support <strong>added<\/strong>\n<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.FileCollection.AddUsingPath<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.FileCollectionAddParameters<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.FolderCollectionAddParameters\n<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.List.AllowDeletion<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.List.SaveAsTemplate<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.List.SyncFlowCallbackUrl\n<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.ListItem.IconOverlay<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.ListItem.Properties<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.ListItem.UpdateOverwriteVersion\n<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Web.SiteLogoDescription<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Web.ThemedCssFolderUrl\n<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.TenantCdn.TenantCdnUrl.ExpirationTimeUtc\n<\/li>\n<\/ul>\n<h2>Microsoft.Online.SharePoint.Client.Tenant<\/h2>\n<p>Following properties have been <strong>removed<\/strong>.<\/p>\n<ul>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantAdministration.Tenant.BlockAccessForUnmanagedDevices<\/li>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.BlockAccessForUnmanagedDevices\n<\/li>\n<\/ul>\n<h2>Microsoft.ProjectServer.Client<\/h2>\n<p>Following property has been <strong>removed<\/strong>.<\/p>\n<ul>\n<li>public <strong>enum<\/strong> Microsoft.ProjectServer.Client.QueueMsgType<\/li>\n<\/ul>\n<p>Following properties have been <strong>added<\/strong>.<\/p>\n<ul>\n<li>public <strong>property<\/strong> Microsoft.ProjectServer.Client.DraftTask.TaskType<\/li>\n<li>public <strong>property<\/strong> Microsoft.ProjectServer.Client.PublishedTask.TaskType<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><span style=\"font-size: large\"><em>&ldquo;Sharing is caring&rdquo;<\/em><\/span><\/p>\n<hr>\n<p><i><a href=\"https:\/\/twitter.com\/vesajuvonen\">Vesa Juvonen<\/a>, Senior Program Manager, OneDrive-SharePoint Engineering, Microsoft &#8211; 24th&nbsp;of November&nbsp;2016<\/i><\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"<p>We are happy to announce availability of new&nbsp;SharePoint Client Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release<\/p>\n","protected":false},"author":69217,"featured_media":643,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[9],"tags":[],"class_list":["post-642","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sharepoint-framework"],"acf":[],"blog_post_summary":"<p>We are happy to announce availability of new&nbsp;SharePoint Client Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/642","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69217"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=642"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/642\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/643"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}