The PnP Core SDK is an SDK designed to work for Microsoft 365. It provides a unified object model for working with SharePoint Online and Teams which is agnostic to the underlying APIs being called. The initial goal for this library will be to cover the needs of developers working with either SharePoint Online or Teams, but we're also open to extend this library further towards other Microsoft 365 workloads if there's community demand for doing so.
Packages and status 🏭
| Nuget package | Downloads | Stable | Preview |
|---|---|---|---|
| PnP.Core |  |
 |
 |
| PnP.Core.Auth |  |
 |
 |
| PnP.Core.Admin |  |
 |
 |
| PnP.Core.Transformation |  |
soon |  |
| PnP.Core.Transformation.SharePoint |  |
soon |  |
Getting started 🚀
For more details on how to get started with the PnP.Core SDK checkout our documentation.
I want to help 🙋♂️
If you want to join our team and help, then checkout the How can I help section in our docs.
Supportability and SLA 💁🏾♀️
This library is an open-source and community provided library backed by an active community supporting it. This is not a Microsoft provided library, so there's no SLA or direct support for this open-source component from Microsoft. Please report any issues using the issues list.
Frequently Asked Questions ❓
Will this work in modern .NET
Absolutely! One of the key reasons for building PnP Core SDK is to nicely fit into modern .NET development:
-
We currently target .NET Standard 2.0, .NET 5.0 and .NET 6.0. Use the .NET 6.0 build if you're using a modern .NET version as that's a LTS version, use .NET Standard 2.0 for backwards compatibility with .NET Framework 4.6.1+
-
This library will work cross platform (Windows, Linux, MacOS)
-
This library will work in all places where .NET will work (see our samples to learn more):
- Backend: e.g. Azure functions v3/v4
- Web: e.g. ASP.NET core, Blazor
- Browser (WebAssembly (WASM)): Blazor. We only support Blazor with our .NET 5.0 and .NET 6.0 versions
- Windows Client: Windows Forms, WPF
- Mobile: Xamarin
-
The library internally uses dependency injection and you can consume it via dependency injection in your applications
What underlying APIs are used
The SDK provides an object model that's API agnostic, when you as a developer for example load a model (List, Team, Web,...) the SDK will use the best possible API for loading that model being for the most part Microsoft Graph v1.0 and SharePoint REST. Depending on the needs the SDK will use Microsoft Graph Beta calls and in some cases the CSOM endpoint (client.svc) is called. But the good thing is that all of this is transparent for you as developer! You'll have a consistent development experience regardless of the underlying APIs being called.
As Microsoft Graph is our recommended API to work with Microsoft 365, the SDK will favor Microsoft Graph whenever it makes sense, the "fall back" to SharePoint REST only happens when Microsoft Graph can't provide the needed data or consistency.
What's the relationship with the existing PnP Framework library
The PnP Framework library is very popular library that extends SharePoint using mainly CSOM. This library contains the PnP Provisioning engine, tons of extension methods, etc...but this library has also organically grown into a complex and hard to maintain code base. One of the reasons why the PnP Core SDK development started is to provide a new clean replacement for PnP Framework with a strong focus on quality (test coverage above 80%, automation). As this transition will take quite some time and effort, we plan to gradually move things over from PnP Framework to the PnP Core SDK. Going forward PnP Framework features will move to the PnP Core SDK in a phased approach.
Community rocks, sharing is caring!
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.