Converting SharePoint on-premise A pps to Office 365

2. Converting SharePoint on-premise Apps to Office 365 Jos Auker-Woor M377

3. Jos Auker-Woor

4. Glossary Depreciated No further development by Microsoft May still work at the moment May disappear in the future Will not support new functionality May in on-premise but not 365

5. Why Now? New 365 Customers Existing customers asking about 365 2016 and beyond Easier to develop and support

6. 2007 – Big Push: SharePoint the development platform Server side code Products but also customisation

7. Solutions and Features Server and client side API Well understood 2016 on premise On premise only Dangerous? Needs outage to install Future?

8. Client Side API Both Depreciated

9. SharePoint Hosted - Client Side API Provider Hosted – External (e.g. Azure), connecting via Client API

11. SharePoint SharePoint Hosted The app and all resources are hosted in your SharePoint farm. Still relies on client side API to access SharePoint. Full Appincluding code

12. On Premise and Cloud Think… Scoped to a Single Site Collection Point solutions, localised web parts etc. Client side API Painful updates No easy access to remote data Browser based code JavaScript, HTML

13. SharePoint SharePoint Hosted The app and all resources are hosted in your SharePoint farm. Still relies on client side API to access SharePoint. Full Appincluding code Provider Hosted On-premise, datacentre or Azure hosted application that links to SharePoint. App Stub in SharePoint to handle authentication via OAuth. App ‘Stub’ OAuth Client API

14. On Premise and Cloud External to SharePoint Easy updates (but everyone gets them) Access data remote data Client side API ‘Provider’ and Browser based code JavaScript, C#, anything Dedicated Server/Site Azure

15. Our approach

16. Consistent Styling Include pages, menus, etc. Can cross site collections Store settings Multiple customers Bulk data access

17. We had concerns so… SharePoint Hosted?

18. Consistent Styling Include pages, menus, etc. Can cross site collections Store settings Multiple customers Bulk data access

19. Provider Hosted?

20. Consistent Styling Include pages, menus, etc. Can cross site collections Store settings Multiple customers Bulk data access

21. Demo Patterns and Practices: https://github.com/OfficeDev/PnP Provider Hosted App Full immersion

23. Server Side vs Client Side SPListlist = SPContext.Current.Web.Lists["News"]; SPListItemitem = list.GetItemById(1); lTitle.Text = item["Title"].ToString();

25. Server Side SPSecurity.RunWithElevatedPrivileges(() => { using (SPSitesite = new SPSite("http://server/site/subsite/")) { using (SPWeb web = site.OpenWeb()) { SPListlist = web.Lists["News"]; SPListItemitem = list.GetItemById(1); lTitle.Text = item["Title"].ToString(); } } });

27. Storing Settings

28. Server Side Web Part Settings Property Bag Web Site Collection Web App (root site collection) Web.AllProperties.Add(id, value); … string value = web.AllProperties[id];

29. App Parts

30. Immersion

31. Azure DocumentDB • JSON • No need for pre-defined schema • Standard Queries • Easy to connect from C#, Javascriptetc

32. Bulk Data Access

33. Three approaches we’ve used:

34. Three approaches we’ve used:

35. Three approaches we’ve used:

36. Throttling

37. Throttling – Possible causes • Repeated actions • Bulk updates • Looks like load testing

38. Beware Administrators and PowerShell…

39. Throttling • No Published Rules • Excellent MSDN Article: dn889829 • https://msdn.microsoft.com/EN-US/library/office/dn889829.aspx • Almost always code

40. Throttling – Two Stage • 429 – To many requests • 503 – Server Unavailable

41. Throttling - Avoiding • ClientContext.ExecuteQueryWithIncrementalRetry(retries,delay) • E.g.ctx.ExecuteQueryWithIncrementalRetry(5, 30000); • Cache where possible, Keep calls to a minimum • Make actions ‘irregular’

42. Normal List Throttling Applies SP.ListItemCollectionPosition position = null; stringcaml = "<View><ViewFields><FieldRef Name=‘Title'/>" +"</ViewFields><RowLimit>5000</RowLimit></View>"; do { SP.CamlQueryquery = new SP.CamlQuery() { ListItemCollectionPosition = position, ViewXml = caml }; SP.ListItemCollectionresults = list.GetItems(query); ctx.Load(results); ctx.ExecuteQuery(); position = results.ListItemCollectionPosition; // Do something here with results } while (position != null);

43. Multiple Customers

44. App Site

45. MyApp - Australia DocumentDB SQL Etc

46. MyApp - Australia DocumentDB SQL Etc

47. MyApp - Australia DocumentDB SQL Etc MyApp2 - Singapore

48. Traffic Manager MyApp Traffic Manager MyApp1 - Australia DocumentDB SQL Etc MyApp2 - Singapore

49. Traffic Manager MyApp Traffic Manager MyApp1 - Australia DocumentDB SQL Etc MyApp2 - Singapore

50. What have I found?