{"id":54,"date":"2018-03-30T00:00:00","date_gmt":"2018-03-30T00:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=54"},"modified":"2018-03-30T00:00:00","modified_gmt":"2018-03-30T00:00:00","slug":"new-sharepoint-csom-version-released-for-office-365-march-2018","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/new-sharepoint-csom-version-released-for-office-365-march-2018\/","title":{"rendered":"New SharePoint CSOM version released for SharePoint Online &#8211; March 2018"},"content":{"rendered":"<div id=\"body-content\">\n<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 was mainly a normal monthly maintenance release with only minor changes on the CSOM and PowerShell side.<\/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;<strong><em>Microsoft.SharePointOnline.CSOM<\/em><\/strong>&#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 to the latest version, rather than downloading\u00a0the SDK to your machine.<\/p>\n<p>The version of the newly released CSOM package is <strong>16.1.7521.1200<\/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.\u00a0Notice that even though the NuGet version is increased to 16.1.7521.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\" src=\"https:\/\/officedevblogs.wpengine.com\/wp-content\/uploads\/2018\/05\/SPCSOMNuget16175211200.png\" alt=\"CSOM NuGet at VS2017 NuGet manager\" width=\"1163\" height=\"770\" \/><\/p>\n<p><a href=\"https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=35588\">SharePoint Online Management Shell<\/a>\u00a0has been also updated to match with this CSOM release. You can find a new set of cmdlets listed in this article.<\/p>\n<p><strong><em>Notice<\/em><\/strong>\u00a0that since this NuGet\u00a0package 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\u00a0dependency to your target environment are 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>.\u00a0We 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<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 <strong>added.<\/strong><\/p>\n<ul>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.CheckedOutFile<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.CheckedOutFileCollection<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.CheckedOutFileObjectPropertyNames<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.CheckedOutFilePropertyNames<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.CopyMigrationOptions.AllowSmallerVersionLimitOnDestination<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.List.GetCheckedOutFiles<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.ListItem.SetComplianceTagWithMetaInfo<\/li>\n<li>public <strong>enum<\/strong> value Microsoft.SharePoint.Client.ListPageRenderType.IsUnghosted<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.ScriptSafeDomain<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.ScriptSafeDomainEntityData<\/li>\n<li>public <strong>enum<\/strong> Microsoft.SharePoint.Client.ScriptSafeExternalEmbedding<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.SharingLinkData.IsReviewLink<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.SharingLinkInfo.IsReviewLink<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Site.AllowExternalEmbeddingWrapper<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Site.CustomScriptSafeDomains<\/li>\n<li>public <strong>class<\/strong> Microsoft.SharePoint.Client.SPScriptSafeDomainsCollection<\/li>\n<li>public <strong>property<\/strong> Microsoft.SharePoint.Client.Web.WelcomePage<\/li>\n<\/ul>\n<h2>Microsoft.Office.Client.Policy<\/h2>\n<p>Following properties, classes and methods have been\u00a0<strong>added.<\/strong><\/p>\n<ul>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.CompliancePolicy.SPPolicyStoreProxy.GetListComplianceTag<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.CompliancePolicy.SPPolicyStoreProxy.SetListComplianceTag<\/li>\n<li>public <strong>method<\/strong> Microsoft.SharePoint.Client.CompliancePolicy.SPPolicyStoreProxy.SetListComplianceTagWithMetaInfo<\/li>\n<\/ul>\n<h2>New\u00a0PowerShell cmdlets in SharePoint Online Management Shell release<\/h2>\n<p>Following cmdlets have been added to the latest release of <a href=\"https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=35588\">SPO Managment Shell<\/a>. <strong>Notice<\/strong> that some of the below commands do <strong>NOT<\/strong> work in normal tenants until the capability is truly released and enabled. There will be separate communications around availability fo the new capabilities when they are released<strong>.\u00a0<\/strong><\/p>\n<ul>\n<li>Get-SPOUnifiedGroup<\/li>\n<li>Set-SPOUnifiedGroup<\/li>\n<\/ul>\n<p>PowerShell documentation has been also moved to\u00a0<a href=\"https:\/\/docs.microsoft.com\/en-us\/powershell\/sharepoint\/?view=sharepoint-ps\">docs.microsoft.com platform<\/a> and will be updated more frequently in the future.<\/p>\n<p><span style=\"font-size: large\"><em>\u201cSharing is caring\u201d<\/em><\/span><\/p>\n<hr \/>\n<p><i><a href=\"https:\/\/twitter.com\/vesajuvonen\">Vesa Juvonen<\/a>, Senior Program Manager, SharePoint Engineering, Microsoft &#8211; 30th of\u00a0March 2018<\/i><\/p>\n<\/div>\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. <\/p>\n","protected":false},"author":69217,"featured_media":55,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-54","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. <\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/54","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=54"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/54\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/55"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=54"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=54"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}