Rencore Webinar: SharePoint Customizations - the most overlooked road block to your migration
Download as PPTX, PDF•1 like•1,559 views
The document discusses the challenges and strategies for migrating SharePoint customizations to Office 365 and outlines the differences between full trust solutions and the SharePoint Framework. It emphasizes the importance of assessing existing customizations, reusing components, and adopting modern development practices. The document also covers considerations for authentication and the transformation process to ensure future-proof solutions.
Rencore Webinar: SharePoint Customizations - the most overlooked road block to your migration
- 1. w: rencore.com | e: [email protected] | t: @rencoreab SharePoint Customizations The most overlooked road block to your migration
- 2. Erwin van Hunen Product Owner - Transformation MVP Office Servers and Services Microsoft Certified Master [email protected] www.spcaf.com/blog @erwinvanhunen
- 4. Full Trust Code vs. „App“ „Addin“ rencore.com Package/Application/Code that uses • Server Side Object Model • Declarative Code • Infrastructure specific components (e.g. HTTP Handlers) • (Too?) High level of trust Package/Application/Code that uses • Client Side Object Model / REST • Runs with Office365 • Runs outside the SharePoint box • Configurable, but complex level of trust
- 5. Full Trust Code vs. SharePoint Framework rencore.com Package/Application/Code that uses • Server Side Object Model • Declarative Code • Infrastructure specific components (e.g. HTTP Handlers) • (Too?) High level of trust Package/Application/Code that uses • Client Side Object Model / REST • Based on JavaScript / TypeScript • Not yet available for SP 2016 • Has the same rights as the user running it
- 6. “Will you ever support farm solutions in Office 365?” Farm solutions are deployed cross SharePoint farm and they’d impact multiple customers… No. Vesa Juvonen, Microsoft
- 8. rencore.com
- 10. rencore.com
- 11. What does Transformation mean? rencore.com • Look at what you have, then • Implement from scratch, while • Re-using concepts, patterns and data
- 12. Why would you Transform? rencore.com • Moving from on-prem to Office365 or Hybrid • SharePoint version update • To be 'future proof' • Changed / New Requirements • Cannot start on a greenfield (time, money, complexity) • Maintenance problems caused by customizations
- 13. How would you Transform your Code? rencore.com • Replace / gradually update existing FTC components • Re-use code / data structures / solution concepts/ integrations
- 15. Major Changes rencore.com • No SSOM, use CSOM/REST/Graph • Do not use the Feature Framework • Avoid Declarative artifacts / CAML where possible (WebTemplates, Content Types, etc.) • Do not use MasterPages • Minimize Branding • Approach SharePoint/Office365 as a service • ”Modern” web development technologies (SPFx) instead of .NET
- 16. CAML == BAD rencore.com Custom Web Template onet.xml X feature activations onet.xml X feature activations onet.xml X feature activations +2 onet.xml X feature activations +4 onet.xml X feature activations onet.xml X feature activations << Copy >> Significant differences on the outcome unless web template onet.xml has been updated cross site collections with the changes which were also done for out of the box team site. Web Template onet.xml is created by copying team site onet.xml and by adding stapled features to the onet.xml Service updates for introducing new capabilities to team sites also using feature stapling Source:TEE2015DEV-B308 http://matte.in/TTE2015Transform
- 18. Transformation != CTRL + V rencore.com • Is SharePoint/Office365 providing already the functionality? • Does your solution benefit from the SharePoint UI? • Are you relying on 3rd party systems? • Does it have to be SharePoint? • Are the business requirements still valid?
- 19. The Transformation Process rencore.com Learn Plan & Track TransformAssess
- 20. Readiness rencore.com • Add-in Model techniques • App Part • Full Immersive app • UI Custom Actions • Remote Provisioning • Client Parts / SPFx • Hosting • on-prem/Office365, • Provider/SharePoint hosted • Authentication • On-prem AD or Azure AD?
- 22. Code Assessment rencore.com • Understand which customizations you have • Understand what they do • Understand why you have them and if they are still relevant • Understand the impact they make on the environment • Understand the involved effort to transform
- 23. Consider Authentication Carefully rencore.com • If you transform your solution to SharePoint Online: • Do you have an on-prem AD? • Do you use ADFS? • Are you moving to Azure AD? • Will you use Hybrid? • Will you use explicit or implicit grant flow for authentication?
- 24. Consider Authentication Carefully rencore.com • If you transform your solution to SharePoint Online: • Do you have an on-prem AD? • Do you use ADFS? • Are you moving to Azure AD? • Will you use Hybrid? • Will you use explicit or implicit grant flow for authentication?
- 25. Development: Add-In Model rencore.com • Complex security • Add-in security vs User security • Limited ability to specify what the add-in wants to do • Powerful: full access to C# / .NET ecosystem • Rich APIs • CSOM • REST • Microsoft Graph
- 26. Development: SharePoint Framework rencore.com • Not a replacement for Add-Ins but rather another option • Simple security • The solution users has the same rights as the user using it • Powerful: access to the full JavaScript ecosystem • Rich APIs • JSOM • REST • Microsoft Graph
- 27. Deployment rencore.com FULL TRUST •WSP files •Full control over server •Flexible •With great power comes great responsibility SANDBOX •WSP files •No control over server •Less flexible •With less power comes great frustration APPS / ADD-INs •Still new to many people •Separate hosting model •Complex authentication model SPFx •Still in preview •Separate hosting model •Potentially very new development model to 'traditional' SP Devs
- 28. Move to Remote Provisioning rencore.com • 'Roll your own' • Complex, high maintenance • Flexible and potentially build for the task • Use the PnP Provisioning Engine • Tested, pre-built • Template approach • Code approach • Extensible • Use the PnP Partner Pack • Based upon the PnP Provisioning Engine
- 29. Resources rencore.com Office Pattern & Practices • https://dev.office.com/pnp • Community project lead by Microsoft • Core Library, PowerShell cmdlets, samples, reference implementations • Endorsed by SharePoint product group SharePoint Framework (SPFx) • https://dev.office.com/sharepoint • Additional development model • Still in preview
Editor's Notes
- #7: M