{"id":3762,"date":"2019-11-29T01:58:56","date_gmt":"2019-11-29T09:58:56","guid":{"rendered":"https:\/\/developer.microsoft.com\/en-us\/office\/blogs\/?p=3762"},"modified":"2019-11-29T01:58:56","modified_gmt":"2019-11-29T09:58:56","slug":"new-sharepoint-csom-version-released-for-sharepoint-online-november-2019","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/new-sharepoint-csom-version-released-for-sharepoint-online-november-2019\/","title":{"rendered":"SharePoint CSOM version released for SharePoint Online &#8211; November 2019"},"content":{"rendered":"<p>We are happy to announce the availability of new\u00a0SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. This release is mainly a small maintenance release with a minimal set of changes in the CSOM API and PowerShell cmdlets.<\/p>\n<p>You can find the latest CSOM package for SharePoint Online, including the Project Online CSOM assembly, from the\u00a0<a href=\"https:\/\/www.nuget.org\/packages\/Microsoft.SharePointOnline.CSOM\">NuGet gallery<\/a>\u00a0with an id of &#8216;<strong><em>Microsoft.SharePointOnline.CSOM<\/em><\/strong>&#8216;. We do recommend you to use the NuGet Package to gain access to the latest version, rather than downloading\u00a0the SDK to your machine as we do not update the separate MSI installer for SharePoint Online CSOM anymore.<\/p>\n<p>The version of the newly released CSOM package is <strong>16.1.19515.12000<\/strong>. Previous\u00a0versions of the NuGet have\u00a0<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. Notice that even though the NuGet version is increased to 16.1.19515.12000, 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>Notice that we did change our version numbering from 4 digit number to 5 digit number recently for SharePoint Online. This is related on avoid overlap with the SP2019 version numbers. We are also working now actively on <strong>new .NET Standard version of CSOM package<\/strong> and are planning to get it released later this autumn first as a preview release and then followed up with monthly release cycle as we do with old NuGet package.<\/p>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3380 size-full\" src=\"https:\/\/officedevblogs.wpengine.com\/wp-content\/uploads\/2019\/11\/csom-161515.png\" alt=\"NuGet Package Manager in VS2019 with CSOM NuGet package selected\" width=\"900\" height=\"607\" \/><\/p>\n<p><a href=\"https:\/\/www.powershellgallery.com\/packages\/Microsoft.Online.SharePoint.PowerShell\">SharePoint Online Management Shell<\/a> has been also updated to match with this CSOM release from the API perspective. There was no new cmdlets with this release.<\/p>\n<p><strong><em>Notice<\/em><\/strong>\u00a0that since this NuGet\u00a0package is targeted to <strong>SharePoint Online<\/strong>, you <strong>cannot<\/strong> use it directly in on-premises environments (SharePoint 2013, 2016 or 2019). This is because of the server side dependencies of the APIs. CSOM versioning model and\u00a0dependency\u00a0on\u00a0your target environment are clarified in following blog post &#8211;\u00a0<a href=\"http:\/\/dev.office.com\/blogs\/using-correct-csom-version-for-sharepoint-customizations\">Using correct Client-Side Object Model (CSOM) version for SharePoint customizations<\/a>.\u00a0We have released separate NuGet packages for on-premises. See following blog post for additional details &#8211;\u00a0<a href=\"https:\/\/developer.microsoft.com\/en-us\/sharepoint\/blogs\/updated-versions-of-the-sharepoint-on-premises-csom-nuget-packages\/\">Updated versions of the SharePoint on-premises CSOM NuGet packages<\/a>.<\/p>\n<h2>New properties and methods\u00a0across assemblies<\/h2>\n<p>Here&#8217;s a raw list of all the changes in the classes,\u00a0properties and methods within this package.<\/p>\n<h2>Microsoft.SharePoint.Client<\/h2>\n<p>Following properties, classes and methods have been\u00a0<strong>added.<\/strong><\/p>\n<ul>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.CountByDate<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Field.IndexStatus<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.FileCollectionAddParameters.XorHash<\/li>\n<li>public <strong>enum<\/strong> value Microsoft.SharePoint.Client.ListTemplateType.ContentCenterPrimeLibrary<\/li>\n<li>public <strong>enum<\/strong> value Microsoft.SharePoint.Client.ListTemplateType.ContentCenterSampleLibrary<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.RecentList<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.RecentListCollection<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Site.SearchBoxPlaceholderText<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Site.SensitivityLabelId<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.SPImageItem<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Web.NavAudienceTargetingEnabled<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Web.SearchBoxPlaceholderText<\/li>\n<li>public <strong>enum<\/strong> Microsoft.SharePoint.Client.Sharing.BlockDownloadLinksFileType<\/li>\n<\/ul>\n<h2>Microsoft.Online.SharePoint.Client.Tenant<\/h2>\n<p>Following properties, classes and methods have been\u00a0<strong>added.<\/strong><\/p>\n<ul>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantAdministration.HubSiteProperties.ParentHubSiteId<\/li>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.AuthContextStrength<\/li>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.BlockDownloadLinksFileType<\/li>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantAdministration.Tenant.BlockDownloadLinksFileType<\/li>\n<li>public <strong>enum<\/strong> Microsoft.Online.SharePoint.TenantManagement.BlockDownloadLinksFileTypes<\/li>\n<li>public <strong>property<\/strong> Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.BlockDownloadLinksFileType<\/li>\n<\/ul>\n<p><span style=\"font-size: large\"><em>\u201cSharing is caring\u201d<\/em><\/span><\/p>\n<hr \/>\n<p><i>SharePoint Team, Microsoft &#8211; 29th of November 2019<\/i><\/p>\n","protected":false},"excerpt":{"rendered":"<p>We are happy to announce the availability of new\u00a0SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. November2019 release.<\/p>\n","protected":false},"author":69078,"featured_media":3765,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3762","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer"],"acf":[],"blog_post_summary":"<p>We are happy to announce the availability of new\u00a0SharePoint Client-Side Object Model (CSOM) version targeted for the Office 365 or more specifically for SharePoint and Project Online. November2019 release.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3762","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\/69078"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=3762"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3762\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/3765"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=3762"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=3762"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=3762"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}