Upload
nccomms
View
134
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Once you go app you don't go back
Citation preview
§
Once you go app..AN SHAREPOINT 2013 APP MODEL OVERVIEW
DANIEL SÖRLÖV & ALEXANDER VON MALACHOWSKI
Agenda
Introduction
30,000-feet perspective
Application demo
Daniel Sörlöv
Microsoft Certified Trainer since 2006
Works at Connecta as Senior SharePoint Arkitekt
Microsoft Most Valuable Professional (MVP)
Member of Microsoft Extended Experts Team (MEET)
Member of Springboard Series Technical Experts Panel (STEP)
Alexander von Malachowski
Microsoft Certified since 2009
Working at Connecta as SharePoint Developer
Blogger on PowerShellTaskForce.com
Why use the App Model?
Increased performance
Increase Power User and Site Owner capabilities
Reduce development cost
Overviewable operational costs
Reduce upgrade costs
Use ”OOTB” apps more
What?!
SharePoint 2007 SharePoint 2010 SharePoint 2013
Sharepoint Sharepoint Something Else
SharepointEvents
API
Basics please!
Consider it as a external application
Lives outside of SharePoint
Not even in SP farms
Can use any capability of the plattform on which it rums
Communicates with SharePoint by Client APIs
Security
Does not run in SharePoint farm
Can access data if allowed
Can be fully trusted by Oauth
Security must be addresses outside of SharePoint
Apps
Can be embedded as app-parts
Can be used as SharePoint extensions
Can use its own chrome
Can be managed by site owners!
Positives
Isolated
Multi-tennant
Other development stacks
Easy deploy
Easy to maintain*
Manageable
* let’s assume it for now and get back to it later
Limitations
No Deploying code to /_layouts
No Web templates
No reusable workflow actions
No reusable web services
No Connected webparts
No timer jobs
No BCS (limited to Odata)
No Farm Solutions
Suggested apps
Fullscreen apps
App parts
Workflows
Remote event receivers
Menu and Ribbon actions
Custom Lists, Fields, and Views
AppsEnd-UserPerspective
App Types
Provider hosted app
Auto hosted app
SharePoint Hosted*
* not cloud
Provider hosted
SharePoint Website
Your app!CSOM/Rest + OAuth
You design, host and manage your own plattform!
LAMP?
Auto hosted app
SharePoint Website
AzureCSOM/Rest + OAuth
You design the software and publish it automatically to Azure
SharePoint hosted
SharePoint Website
AppWeb
Reuse SharePoint components, no server code allowed.
Hosting Comparison
Cloud Hosted SharePoint Hosted
Scoping Tenant or Site Site
Architechture Multi-tenant Single-tenant
Developer features Full stack SharePoint+HTML
UI features Any stack SharePoint+HTML
Server Code Any None
Storage Any Lists and Libraries
Server code Any None
When to use SharePoint Hosted?
Good for smaller apps
Isolation
No server code
Clientside
When to use Cloud Hosted?
The world of possibilities
Integrating SharePoint apps
Full page
Parts
Menu/Ribbon extensions
Application identities
SP2010
Sandbox = under user context, no RunWithElevatedPrivileges
Farm = To much permissions, RunWithElevatedPrivileges
SP2013
Installing an app gives no permission to app
Explicitly given to a very specific scope
Builds on Oauth tokens
Permissions
You can give Read, Write, Manage and Full Control..
..Site, Web, List, Tenant
Given to a scope, and by that all it’s children
Remote API
Your code
JavaScript Silverlight .Net
CSOMRESTODATAJSON
_API (SharePoint)
Technical Infrastructure Requirements
Wild card entry for app domain
Apps Service Application And Subscrioption Service must be started
App catalog most be created
SharePoint
HostedDemo
Thank you!
Daniel Sörlöv Twitter: @sorlov
http://www.powershelltaskforce.com
http://sorlov.azurewebsites.net
http://facebook.com/sorlov
Alexander von Malachowski Twitter: @a_von_m
http://www.powershelltaskforce.com