1. Transforming SharePoint Farm Solutions to the Add-in Model
Matthias Einig, MVP, CEO
w: rencore.com | e: |

2. Microsoft SharePoint Server 2013
Matthias Einig
CEO, SharePoint MVP
Munich, Germany
@mattein
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Basics

4. Full Trust Code vs. “App” “Addin”
Package/Application/Code that uses
Server Side Object Model
Declarative Code
Infrastructure specific components (e.g. HTTP Handlers)
Package/Application/Code that uses
Client Side Object Model / REST
Could run with Office365
Runs off the SharePoint box

5. “Will Farm Solutions be supported with SharePoint Server 2016”
Yes.
Vesa
We will make though investments mainly on the app model side also for on-premises to better align the development story: Write once and use it cross cloud and on-premises
Vesa Juvonen, Microsoft

6. “Will you ever support farm solutions in Office 365?”
Vesa:
Time: 42:00
Farm solutions are deployed cross SharePoint farm and they’d impact multiple customers…
Vesa Juvonen, Microsoft

7. Transforming your code
11/10/2018
Transforming your code
From farm solutions and full trust code…
To app model…
Vesa
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Microsoft SharePoint Server 2013
What is “Transformation”?
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Transformation != Migration

12. What does transformation mean? ”re-using concepts, patterns and data”
“look at what you have”
then
“implement from scratch”
while
”re-using concepts, patterns and data”

13. Microsoft SharePoint Server 2013
Why?
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Why would you transform?
Moving from on-prem to Office365 or Hybrid
SharePoint version update
Changed / New Requirements
Cannot start on a greenfield (time, money, complexity)
Maintenance problems caused by customizations

15. How?

16. How would you transform your code?
Replace / gradually update existing FTC components
Re-use code / data structures / solution concepts/ integrations

17. Microsoft SharePoint Server 2013
Major Changes
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. Major Changes No SSOM, use CSOM/REST Avoid Feature Framework
Avoid CAML (WebTemplates, Content Types, etc.)
Avoid MasterPages
Minimize Branding
Run code outside of SharePoint (Client, Provider)
Consider SharePoint/Office365 as a service

19. << Copy >>
CAML == BAD
Web Template onet.xml is created by copying team site onet.xml and by adding stapled features to the onet.xml
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.
onet.xml
X feature activations
onet.xml
X feature activations
onet.xml
X feature activations
Custom Web Template
<< Copy >>
Team Site
onet.xml
X feature activations
onet.xml
X feature activations +2
onet.xml
X feature activations +4
Time
Service updates for introducing new capabilities to team sites also using feature stapling
Source: TEE2015 DEV-B308

20. Microsoft SharePoint Server 2013
Reimagine!
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. Transformation != CopyPaste
Is SharePoint/Office365 now 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?

22. Microsoft SharePoint Server 2013
Process
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. The Transformation Process
Assessment
&
Planning
Development
Testing
Deployment
Readiness

24. Readiness App Model techniques Hosting App Part Full Immersive app
UI Custom Actions
Remote Provisioning
Hosting
on-prem/Office365,
Provider/SharePoint hosted

25. “New” provisioning approaches
Provider Hosted App using CSOM/REST’
.NET Console App using CSOM/REST
PowerShell
using CSOM/REST
SharePoint Hosted Apps using
REST/JSOM
PnP
Provisioning Engine
”Mechanical Turk”

26. Assessment: Requirements
Discuss existing solution with the business.
Discuss the requirements with the business.
Learn how the existing customization are used
Decide what to keep, change and remove.

27. Assessment: Code Understand what customizations you have.
Understand what they do.
Understand why you have them and if you need them.
Understand the impact they make on the environment.
Understand the involved effort to transform.

28. Development Office Pattern & Practices
Community project lead by Microsoft
Core Library, PowerShell cmdlets, samples, reference implementations
Approved by SharePoint product group

29. Demo Transformator

30. Deployment In Place Swing Pros: Less customer impact
Less hardware and tooling require
Can be performed with minimal downtime
Cons:
Harder to track progress
Increased possibility of “Orphans”
Swing
Pros:
Total isolation from Production
Clean environment
Cons:
Increased hardware and tooling required
Increased downtime for users (eg. Content Migration)
Source: MVA Training

31. Summary Understand the target platform and technology
Understand the existing solution and requirements
Reimagine and plan the solution
Transform
Deploy and Migrate Content

32. Resources SharePoint Code Analysis Framework http://www.spcaf.com
MVA Training
TechEd Europe Session
OfficeDev Patterns & Practices

33.
@mattein

34. Microsoft SharePoint Server 2013
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.