View
236
Download
0
Category
Preview:
Citation preview
Alex RandallSenior Consultant, SharePointMicrosoft
When and When Not To Use the New SP2013 App Model
When and When Not to Use the New SP2013 App ModelOverview of App Model
When to use it
When NOT to use it
Gray Areas
“To app or not to app” (Decision Matrix)
Demo
What is an “app for SharePoint?”
An “app for SharePoint”…Is a web application that is registered with SharePointFacilitates easy install/uninstall
Handles cross-domain issues
Provides App Isolation
Survives upgrade to future SP versions
Integrates cloud-based resources
Keeps SharePoint performing well
Uses cross platform standards
Works with SP2013 on prem or cloud
Uses Client APIs
SharePoint 2013 Client APIs
JavaScript
REST
.NET
App Model “hosting option” determines what API(s) you can use
apps for SharePoint Hosting OptionsCloud
SharePoint-hosted
SharePoint
Autohosted
Windows Azure and SQL Azure
Provider-hosted
Dedicated server or hosting service
CSOM/REST + OAuth
Host web
App web(optional)
Host web
App web
CSOM/REST + OAuth
Much more info at:
Hosting options for apps for SharePointhttp://msdn.microsoft.com/en-us/library/fp179887.aspx
Host web
App web(optional)
Demo
Things that an app for SharePoint can do
When to use the new SP2013 App Model?
Full s
creen p
ag
es
App Parts
Work
flow
sCustom Ribbon/Menu Actions
Data from other systemsDocument Libraries/Lists/Custom Fields/Views
Many more scenarios!
When NOT to Use the New SP2013 App ModelJust some examples:
Functionality outside the scope of the client APIs
Server-side SharePoint object model
Site definitions
Web templates (host web)
Deploying assets to /_vti_bin or /_layouts Timer Jobs
SharePoint 2013 Themes
Connectable App Parts
Gray Areas= Things that you can do in an app for SharePoint, but perhaps there are:
limitations or alternative ways to do it
Out of box Web Parts
Only in “SharePoint-hosted” apps for SharePoint hosting type
Remote Event Receivers
Only in “Autohosted” or “Provider-hosted” apps for SharePoint hosting types
External data
BCS supports only OData connections in the App Model
Alternatives: 1) Create your own OData wrapper
outside of the app for SharePoint
2) Write code instead of using BCS
“To App or Not To App” (Decision Matrix)1) Out of box SP capabilities?
2) App already exists?
3) Lite customization tools?
4) App Model?
5) Only as a last resort – farm/sandbox solution?
My Twitter@alex_randall_
My Bloghttp://aka.ms/alex
Apps for Office Dev Center
http://dev.office.comSign up for free SP2013 O365 Developer
Account to create apps for SharePoint today!
Thanks!
Thanks for filling out the eval!
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.
Recommended