1. 06 | Practices for Converting existing sites to app model functionality
Vesa Juvonen | Senior Program Manager
Steve Walker | Senior Program Manager

2. Module Overview Transformation process
Assessment
Planning
Implementation
Learnings from field regarding actual projects
Transformation guidance
Different assets and how to work with them

3. Vision EXTEND OFFICE EVERYWHERE CONNECT TO OFFICE 365 SERVICES
BUILD USING AN OPEN PLATFORM
Delve z
Users and groups
Files
Mail
Calendar
My Apps
Video Portal
Contacts
Office Graph
Presentations
Documents
Spreadsheets
Lync
OneNote
Yammer

4. Recommendations Perform careful assessment
Concentrate on functionality
Existing content can be a challenge
Use available tooling and guidance

5. Planning actual transformation tasks
Transformation process
Planning actual transformation tasks

6. Approaching transformation
Readiness
Solution Assessment
Solution Planning
Development & Testing
Deployment
Obtain proper understanding on for the app model
Hosting decisions
Solution package assessment one by one
Can be partly automated with existing tooling
Analyze requirements
Initial high level planning based on functional and business requirements
Detailed technical planning
Actual development and testing based on previous steps
Deployment of apps
Transforming content
Retract solutions

7. SPCAF Professional / Server Edition Commercial Product
SPCAF Community Edition
FREE
SPCAF Migration Assessment
FREE

8. SPCAF Migration Assessment – Analysis rules
Analysis rules for the migration assessment are open source for input from community
Enables faster development cycles and contributions from community
Located under the official Office Dev location in the GitHub
Join us on the transformation rule development!

9. SPCAF tooling in practice

10. How to rationalize your options
Transformation Approaches
How to rationalize your options

11. Transformation Approaches
In Place
Swing
Pros:
Less customer impact (overall)
Less hardware and Tooling required
Can be performed with no down time
Cons:
Harder to track progress
Increased possibility of “Orphans”
Pros:
Total isolation from Production Environment until ready
Clean environment (no “Cruft” from previous FTC code
Cons:
Increased hardware and tooling requirements
Increased downtime for users (can be minimized, but not eliminated)

12. How to approach individual elements
Transformation Guidance
How to approach individual elements

13. Challenge? Existing sites are dependent on full trust code…
Existing content is dependent on declaratively deployed artifacts (Content Types, Site Columns)

14. Replace page layouts and master pages
Gradual reduction of FTC dependency from page layouts and master pages
Implemented as remote operation to control the elements used on sites

15. Replacement of web parts and controls
Remote operation to replace web parts on page
Replace with pre-configured out of the box web parts
Replace with App part instances
Embedded JavaScript
App part installation requires enabling of app side loading in the site
Can be enabled only at the needed time by using CSOM with feature activations

16. Side loading & Page Manipulation

17. Site columns and content types
If created declaratively using feature framework, only solution would be a content migration using third party tooling
If created using code, no actual dependencies on FTC code or farm solutions
Known Issue. We have a plan to address this with new product capability

18. Modules (Feature Framework)
These are essentially files deployed to the site
You should follow the same “remote provisioning pattern” that we outlined for application artifacts such as .webpart files, page layouts and master pages.
EITHER: Touch the file to copy to Content Database OR delete the file and copy afterwards.

19. Site Templates & Web Templates
Site Templates & Web templates themselves aren’t the real problem. It is the FEATURES and ARTIFACTS within that you need to think about
These should be analyzed just like any other farm solution
Replacement method based on artifacts contained within

20. Timer jobs
No ability to create and manage timer jobs within SharePoint, BUT
Scheduling can be done using any external platform
Access to SharePoint and other services using CSOM/REST
Scheduled execution which accesses the needed resources from the SharePoint service and performs the required automation.
Can use either specific account for connection or oAuth based app-only token approach
SharePoint Service 2
Provider Hosted Apps 1
Remote Timer job

21. Remote Timer Jobs

22. Remember!
Deactivate your custom features BEFORE you retract the solution…
It leaves references behind if you do not. Your next upgrade will FAIL.

23. Will require content migration…
Case of a bad headache?
Custom fields types
Custom site definitions
Custom list definition
Moving from publishing to non- publishing sites
Will require content migration…

24. Recommendations Perform careful assessment
Concentrate on functionalities
Existing content can be a challenge
Use available tooling and guidance

25. aka.ms/OfficeDevPnP Transform your code 100+ Visual Studio projects
1/1/2019
aka.ms/OfficeDevPnP
Transform your code
Providing App Model Patterns for common scenarios Open source and based on community contributions Constantly evolving set of material for reuse
100+ Visual Studio projects
Common scenarios Branding Site provisioning Remote event receivers
UX component Taxonomy driven navigation And much more…
Patterns and Practices Yammer Group -
© 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.

26. dev.office.com Sign up Explore
Explore
Get trained

27. Feedback
Office 365 Network Share you best practices and join conversations
Stackoverflow Ask deep technical questions to a world-wide set of developers
ged/ms-office
UserVoice Provide suggestions of what you want in future versions