Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SPSBoston 2016-09-10 - Best Practices for Small-Scale Client-Side Development in SharePoint

4,351 views

Published on

We can build real solutions by using SharePoint and Office 365 as service endpoints that provide us with all sorts of critical business data. On the spectrum between power user dev and enterprise development, there’s plenty of room for departmental or even company-wide solutions that work entirely client side. Often the difference between “enterprise” development and the rest comes down to two factors:
• The governance or guidance around deployment
• The size of the development team
In this in-depth session, we’ll look at some better practices for building solutions, storing and managing code, and source code control for smaller size projects that don’t have complex deployment requirements.

Published in: Technology
  • Be the first to comment

SPSBoston 2016-09-10 - Best Practices for Small-Scale Client-Side Development in SharePoint

  1. 1. SPS Boston 2016 is made possible by our Sponsors Mindsharp Contego Cyber Solutions
  2. 2. Champions Bar 6pm LOCATED IN BOSTON MARRIOTT CAMBRIDGE 2 Cambridge Center Cambridge, MA 02142 (1 min walk from Microsoft) http://www.championscambridge.com/
  3. 3. SharePoint Development Model Evolution Sources: 1. Gartner, Inc. 2013. Press Release: http://www.gartner.com/newsroom/id/2599315 2. 451 Research, Hosting and Cloud Study, 2014
  4. 4. Server Side Client Side
  5. 5. Content Editor Web Part SharePoint Framework One-off, quick solutions with JavaScript / HTML embedded directly in the CEWP Code can still be centralized Script Editor Web Part Centralized code artifacts with a light development pipeline Centralized code artifacts with a more robust development pipeline Reusable components (Client Side Web Parts) with a more formal development process Centralized admin and deployment
  6. 6. Data Access / Initial Manipulation "Document Ready" ViewModel / Application Logic Templates Application Styling
  7. 7. Deprecated Deprecated Endpoint /_vti_bin/listdata.svc /_apiDeprecated None SOAP REST https://graph.microsoft.com/v1.0
  8. 8. Widgets in one Site Collection Widget in one tenant/farm, multiple site collections Widgets used across multiple tenants/farms* Store code in a library in a specific subsite  X X Store code in a library in the root site of the Site Collection   X Store code in a Site Collection specifically for client side code O  O Create an actual CDN (Azure, AWS, dedicated server, other commercial CDN provider…)** X O   - Good solution O – Optional solution, potentially overkill X – Not a great choice * - Not referencing any code that would be part of a commercial solution. ** - CDNs or Content Delivery Networks allow “content” to be made highly available to end users everywhere. Code Creep - SharePoint "CDN" by Julie Turner (@jfj1997) If you store your code in a different Site Collection or CDN, you may need to bootstrap it into place.
  9. 9. The easiest way to add Script and Brand your SharePoint and SharePoint Online by John Liu
  10. 10. $.get() Office Dev PnP Web Cast – Introducing Widget Wrangler for SharePoint development RequireJS text plugin
  11. 11. The State Of JavaScript: Front-End Frameworks: A few preliminary results
  12. 12. Sympraxis’ SharePoint Client Side Development Pipeline spsave Code Editor
  13. 13. Sympraxis’ SharePoint Client Side Development Pipeline
  14. 14. Email marc.anderson@sympraxisconsulting.com Twitter @sympmarc Blog http://sympmarc.com SPServices http://spservices.codeplex.com SPXSLT http://spxslt.codeplex.com Books http://sympmarc.com/books The Middle Tier Manifesto http://bit.ly/middletier

×