Nothing matches your search.
All articles
- Development & automation
Migrating privileged SharePoint server-side code requires an authorization design
A WSP that deploys on Subscription Edition has not proved its authorization boundary. Review caller intent, elevated object lifetime, external identities and business acceptance before retaining, refactoring, extracting or eliminating server-side code.
Keep reading → - Development & automation
Farm solution, SharePoint Framework or external service: deciding each customisation on Subscription Edition
A farm that upgrades to Subscription Edition does not make its custom code compatible, secure or supported. Each component is decided on its own: kept as a farm solution, rebuilt on the SharePoint Framework, moved to an external service, or retired. What Microsoft documents for each, and what decides between them.
Keep reading → - Development & automation
Why SharePoint Framework stayed on React 17 through SPFx 1.23.2
A retrospective on the SPFx 1.16–1.23.2 dependency boundary, updated to distinguish it from SPFx 1.24 and React 18.3.1. Platform compatibility requires more than changing a package version.
Keep reading → - Development & automation
Developing for SharePoint Server Subscription Edition: the practices that hold up
Subscription Edition is supported until at least 2035 and its SharePoint Framework ceiling has not moved since 2023. That combination is the whole job: a long runway on an older stack. This is how to build on it well, with code that runs on the version your farm actually accepts.
Keep reading →
Categories
- Keep reading →
AI & agents
6 - Keep reading →
Azure & Cloud
1 - Keep reading →
Company
2 - Keep reading →
Development & automation
9 - Keep reading →
Governance & security
3 - Keep reading →
Microsoft 365 & SharePoint
2 - Keep reading →
Migrations
3
Send us a message
or write to hello@ph7x.com