pnp / pnp/pnpframework

Clarify in Documentation SharePoint Server Support

Open
#1,189 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
259
Forks
161
Avg merge
10h 33m
Merged PRs (30d)
1

Description

In my opinion, an improvement is needed to clarify what editions of SharePoint Server (on-premise) are supported. Reading between the lines on "who should switch", PnP.Framework seems to only support M365 SharePoint Online. It also omits any reference to SharePoint Server Subscription Edition, a successor to 2019.

There also appear to be a number of issues logged in this repo where folks appear to be using PnP.Framework on Server 2019 and Subscription editions, where it's clarified by maintainers that PnP.Framework is not designed to support said Server editions.

ChatGPT AI recommendations unfortunately hallucinate and claim misinformation such as:

“The PnP Framework is a .NET library targeting .NET Framework 4.6.2 and above that builds on top of the SharePoint CSOM. It supports both SharePoint Online and SharePoint on-premises (2013–2019, and Subscription Edition) environments.”

I'd rather a clear markdown table of ✅ and ❌ in the following locations:

Perhaps reusing the heading "Who should switch to PnP Framework?" The same can be said for PNP.Core.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read README.md and docs/using-the-framework/migrating-from-pnp-sites-core.md, especially the existing “Who should switch to PnP Framework?” section. Clarify SharePoint Server edition support with consistent ✅/❌ Markdown tables in both locations, including Subscription Edition, so the supported environments are unambiguous.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.