ses-b401

19
Tips You Need to Know for Creating Apps for Microsoft Office and SharePoint 2013 Chris Johnson SBS-B401

Upload: chris-johnson

Post on 30-Jun-2015

1.311 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: SES-B401

Tips You Need to Know for Creating Apps for Microsoft Office and SharePoint 2013

Chris Johnson

SBS-B401

Page 2: SES-B401

whoami?• www.provokesolutions.com• [email protected]• Blog: www.looselytyped.net• @LoungeFlyZ• Ex-10yr Microsoftie, SharePoint Product

Management, Program Management and Consulting Services

Page 3: SES-B401

Agenda1. DEMO2. DEMO3. DEMO4. DEMO5. DEMO6. DEMO7. DEMO8. DEMO9. DEMO10. DEMO

Page 4: SES-B401

#1 Use SignalR for App tracing and debugging

Page 5: SES-B401

#2 Cache tokens if you need to

Page 6: SES-B401

#3: Use OAuth to access SharePoint from apps for Office

Page 7: SES-B401

OAuth in apps for Office

SharePoint

App Server

OAuth

Page 8: SES-B401

#3 & 4: Use the SharePoint cross-domain library

Page 9: SES-B401

Cross-Domain Library

SharePoint

Firewall

App Server

Page 10: SES-B401

#5: Bring Office documents into your SharePoint apps with WACs

Page 11: SES-B401

#6: Single Page Apps in SharePoint

Page 12: SES-B401

SPA?• Single HTML page• Client script for everything• Communicates with server via JS• Integrates with Browser for navigation

Page 13: SES-B401

SPA Resources• Learn: http://www.johnpapa.net/spa/

• Framework: Durandal • Databinding: Knockout• Layout: Bootstrap• Icons: FontAwesome• Data Queries: LinqJS• Notifications: Toastr

Page 14: SES-B401

#7: App CSS makes your app look like part of the experience

Page 15: SES-B401

App UX design guidelines

Page 16: SES-B401

#8: Elevate your SharePoint app’s permissions with app-only calls

Page 17: SES-B401

#9: Bring your app to where users are by integrating with Yammer

Page 18: SES-B401

#10: Azure web sites + O365 + tfs.VisualStudio.com =

Page 19: SES-B401

© 2013 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.