Mein Blick auf SharePoint & M365 & .NET aus der Sicht eines Full-Stack Entwicklers

In 2012 Microsoft introduced a new development model for SharePoint called "SharePoint Add-In". The goal of the new development approach was to extract custom server side code from SharePoint Server. Because the server side code of classic custom SharePoint Server extensions, like WebParts, Event Receiver or MasterPages with code-behind, are running directly within the SharePoint IIS worker process (w3wp). This means when a custom server side extension throws an exception the whole SharePoint server w3wp process is affected. In such a case the SharePoint page cannot be displayed and the user is frustrated. To mitigate such fatal errors Microsoft tried to move custom code to a separate w3wp process isolated from the SharePoint process. The first approach was the Sandboxed Solutions: Sandboxed solutions are Microsoft SharePoint Foundation features that are deployed into a partially trusted environment referred to as the sandbox. The sandbox is designed to bring greater stabilit...