We are happy to announce the availability of new SharePoint 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.
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 do recommend you to use the NuGet Package to gain access to the latest version, rather than downloading the SDK to your machine as we do not update the separate MSI installer for SharePoint Online CSOM anymore.
The version of the newly released CSOM package is 16.1.19223.1200. Previous versions of the NuGet have 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.19223.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 aligns with the NuGet version.
Notice that we did change our version numbering from 4 digit number to 5 digit number. This is related on avoid overlap with the SP2019 version numbers. We are also working now actively on new .NET Standard version of CSOM package 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.
SharePoint Online Management Shell has been also updated to match with this CSOM release from the API perspective with few new cmdlets.
Notice that since this NuGet package is targeted to SharePoint Online, you cannot 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 dependency on your target environment are clarified in following blog post – Using correct Client-Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details – Updated versions of the SharePoint on-premises CSOM NuGet packages.
New properties and methods across assemblies
Here’s a raw list of all the changes in the classes, properties and methods within this package.
Microsoft.SharePoint.Client
Following properties, classes and methods have been added.
- public property Microsoft.SharePoint.Client.CompanyPortalContext.FooterNavigation
- public property Microsoft.SharePoint.Client.CompanyPortalContext.HubSiteData
- public method Microsoft.SharePoint.Client.Field.DisableIndex
- public method Microsoft.SharePoint.Client.Field.EnableIndex
- public enum Microsoft.SharePoint.Client.FieldIndexStatus
- public method Microsoft.SharePoint.Client.File.FinishUploadWithChecksum
- public method Microsoft.SharePoint.Client.File.GetPreAuthorizedAccessUrl2
- public property Microsoft.SharePoint.Client.RenderListDataParameters.OriginalDate
- public method Microsoft.SharePoint.Client.SPHSite.AddOrgNewsSite
- public property Microsoft.SharePoint.Client.Web.ClassicWelcomePage
- public property Microsoft.SharePoint.Client.Web.IsHomepageModernized
Microsoft.Online.SharePoint.Client.Tenant
Following properties, classes and methods have been added.
- public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.DefaultLinkToExistingAccess
- public property Microsoft.Online.SharePoint.TenantAdministration.SiteProperties.DefaultLinkToExistingAccessReset
- public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetSPOLocaleWebTemplates
- public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.RemoveFromOrgAssets
- public method Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.RemoveFromOrgAssets
“Sharing is caring”
SharePoint Team, Microsoft – 30th of August 2019
