Skip to content

Commit 990d801

Browse files
authored
Update using-csom-for-dotnet-standard.md (SharePoint#7394)
Adding a note about what versions of the CSOM library contain the standard assemblies.
1 parent 2d5408f commit 990d801

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/sp-add-ins/using-csom-for-dotnet-standard.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,10 @@ Support for legacy authentication flows (so called cookie based auth using the `
3131
`Microsoft.SharePoint.Client.Utilities.HttpUtility` class | Yes | No | Switch to similar classes in .NET such as `System.Web.HttpUtility`
3232
`Microsoft.SharePoint.Client.EventReceivers` namespace | Yes | No | Switch to modern eventing concepts such as [Web Hooks](../apis/webhooks/get-started-webhooks.md).
3333

34+
> [!Note]
35+
> .NET Standard version of the CSOM Assemblies are included on the existing NuGet package called Microsoft.SharePointOnline.CSOM from the version 16.1.20211.12000 onwards.
36+
> The below sample requires this version or higher to work in a .Net core/standard targeted project.
37+
3438
## Using modern authentication with CSOM for .NET Standard
3539

3640
Using user/password based authentication, implemented via the `SharePointOnlineCredentials` class, is a common approach for developers using CSOM for .NET Framework. In CSOM for .NET Standard this isn't possible anymore, it's up to the developer using CSOM for .NET Standard to obtain an OAuth access token and use that when making calls to SharePoint Online. The recommended approach for getting access tokens for SharePoint Online is by setting up an Azure AD application. For CSOM for .NET Standard the only thing that matters are that you obtain a valid access token, this can be using resource owner password credential flow, using device login, using certificate based auth,...

0 commit comments

Comments
 (0)