Sys02 best way to create a share point app
Download as PPTX, PDF0 likes272 views
This document discusses different approaches for creating SharePoint apps. It outlines the evolution from apps that live within SharePoint to the new app model where apps communicate with SharePoint via REST/CSOM. The document compares different types of apps and considers what approach may be best. It then provides an agenda covering the UI layer using standard and custom styles, the business layer using JavaScript and custom services, and using server-side code when needed.
Sys02 best way to create a share point app
- 1. Template designed by Best way to create a SharePoint App Fabio Franzini @franzinifabio www.fabiofranzini.com Template designed by
- 2. Template designed by brought to you by
- 3. Template designed by SharePoint MVP Senior Consultant and Software Engineer MCT Trainer, MCPD Web Applications, MCTS SharePoint 2010/2007 Web Stack Lover Official Ignite Trainer for SharePoint 2013 & 2010 in Italy Over 10 years experience in IT as a software engineer About Me
- 4. Template designed by Evolution in SharePoint Development New App Model Kinds of Apps What is the best model? UI Layer Biz Layer Server Side Code Agenda
- 5. Template designed by Declar. App & Workflow Events CSOM _api _api Evolution in SharePoint Development CSOM
- 6. Template designed by Apps no longer live in SharePoint Reduces the ramp-up time for those building apps (Don’t need to know/be as familiar with SharePoint “-isms”) Custom code executes in the client, cloud or on-premise Easier to upgrade to future versions of SharePoint Works in hosted environments w/o limitations Apps communicate with SharePoint via REST / CSOM Apps are granted permissions to SharePoint via OAuth Acquire apps via centralized Marketplace Some Examples http://code.msdn.microsoft.com/officeapps New App Model
- 7. Template designed by Kinds of Apps Provision an Isolated sub web on a parent web Reuse web elements (lists, files, out-of-box web parts) No server code allowed; use client JavaScript for logic, UX Server side code allowed Any web stack allowed Windows Azure + SQL Azure provisioned invisibly as apps are installed
- 8. Template designed by What is the best model (for me)? Hosted Site for Services If you need!
- 9. Template designed by Or…. HTML5 + JavaScript + Server Side Services Any language supported by your web server or hosting service
- 10. Template designed by UI Layer 1/3
- 11. Template designed by Using Standard SharePoint Styles MSDN: http://bit.ly/1hO8ToL, http://bit.ly/KMSzIF Add custom styles Add Prefix to all css styles to prevent conflicts UI Layer 2/3
- 12. Template designed by No PostBack or Server Side Page Rendering Using Client Side Framework for UI Logics and Custom Controls KnockoutJS / DurandalJS (MVVM) / Complete SPA Framework on top of KnockoutJS AngularJS Complete SPA Framework from Google Another or Custom Solution UI Layer 3/4
- 13. Demo UI Layer Styles and Controls
- 14. Template designed by Client Code (JavaScript) + SharePoint Client API (CSOM / REST) + Custom Services (ASP.NET, NodeJS, PHP, Java, …) Modularizing your client code!!!!!! Uses RequireJS for example Biz Layer
- 15. Demo Biz Layer
- 16. Template designed by Every time you need to functionality difficult to do on the client DB Access Long Running Process Server Side Generation … Uses the technology that you want ASP.NET NodeJS PHP JSP …. Server Side Code
- 17. Template designed by What is the best model? SharePoint Hosted + Services / Provider Hosted with Client Side Logics + Services UI Layer Client Side Templating Biz Layer Client Side Code + Services Server Side Code ASP.NET, NodeJS, JSP, PHP… Recap
- 18. Template designed by brought to you by