Your SlideShare is downloading. ×
0
§
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 ...
Alexander von Malachowski


Microsoft Certified since 2009



Working at Connecta as SharePoint Developer



Blogger on...
Why use the App Model?


Increased performance



Increase Power User and Site Owner capabilities



Reduce development...
What?!

SharePoint 2007

Sharepoint

SharePoint 2010

Sharepoint

SharePoint 2013

Sharepoint

API
Events

Something
Else
Basics please!


Consider it as a external application



Lives outside of SharePoint


Not even in SP farms



Can us...
Security


Does not run in SharePoint farm



Can access data if allowed



Can be fully trusted by Oauth



Security ...
Apps


Can be embedded as app-parts



Can be used as SharePoint extensions



Can use its own chrome



Can be manage...
Positives


Isolated



Multi-tennant



Other development stacks



Easy deploy



Easy to maintain*



Manageable
...
Limitations


No Deploying code to /_layouts



No Web templates



No reusable workflow actions



No reusable web se...
Suggested apps


Fullscreen apps



App parts



Workflows



Remote event receivers



Menu and Ribbon actions



C...
Apps
End-User
Perspective
App Types


Provider hosted app



Auto hosted app



SharePoint Hosted*

* not cloud
Provider hosted

SharePoint
Website

CSOM/Rest + OAuth

You design, host and manage your own plattform!
LAMP?

Your app!
Auto hosted app

SharePoint
Website

CSOM/Rest + OAuth

You design the software and publish it automatically to Azure

Azu...
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-te...
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 permiss...
Permissions


You can give Read, Write, Manage and Full Control..



..Site, Web, List, Tenant



Given to a scope, and...
Remote API

_API (SharePoint)

REST
ODATA
JSON

CSOM
JavaScript
Your code

Silverlight

.Net
Technical Infrastructure Requirements


Wild card entry for app domain



Apps Service Application And Subscrioption Ser...
SharePoint

Hosted
Demo
Thank you!

Daniel Sörlöv

Alexander von Malachowski



Twitter: @sorlov



Twitter: @a_von_m



http://www.powershellt...
Upcoming SlideShare
Loading in...5
×

SPCA2013 - Once you go app you don't go back

137

Published on

Once you go app you don't go back

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
137
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "SPCA2013 - Once you go app you don't go back"

  1. 1. §
  2. 2. Once you go app.. AN SHAREPOINT 2013 APP MODEL OVERVIEW DANIEL SÖRLÖV & ALEXANDER VON MALACHOWSKI
  3. 3. Agenda  Introduction  30,000-feet perspective  Application demo
  4. 4. 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)
  5. 5. Alexander von Malachowski  Microsoft Certified since 2009  Working at Connecta as SharePoint Developer  Blogger on PowerShellTaskForce.com
  6. 6. 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
  7. 7. What?! SharePoint 2007 Sharepoint SharePoint 2010 Sharepoint SharePoint 2013 Sharepoint API Events Something Else
  8. 8. 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
  9. 9. 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
  10. 10. Apps  Can be embedded as app-parts  Can be used as SharePoint extensions  Can use its own chrome  Can be managed by site owners!
  11. 11. 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
  12. 12. 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
  13. 13. Suggested apps  Fullscreen apps  App parts  Workflows  Remote event receivers  Menu and Ribbon actions  Custom Lists, Fields, and Views
  14. 14. Apps End-User Perspective
  15. 15. App Types  Provider hosted app  Auto hosted app  SharePoint Hosted* * not cloud
  16. 16. Provider hosted SharePoint Website CSOM/Rest + OAuth You design, host and manage your own plattform! LAMP? Your app!
  17. 17. Auto hosted app SharePoint Website CSOM/Rest + OAuth You design the software and publish it automatically to Azure Azure
  18. 18. SharePoint hosted SharePoint Website AppWeb Reuse SharePoint components, no server code allowed.
  19. 19. 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
  20. 20. When to use SharePoint Hosted?  Good for smaller apps  Isolation  No server code  Clientside
  21. 21. When to use Cloud Hosted?  The world of possibilities
  22. 22. Integrating SharePoint apps  Full page  Parts  Menu/Ribbon extensions
  23. 23. 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
  24. 24. 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
  25. 25. Remote API _API (SharePoint) REST ODATA JSON CSOM JavaScript Your code Silverlight .Net
  26. 26. Technical Infrastructure Requirements  Wild card entry for app domain  Apps Service Application And Subscrioption Service must be started  App catalog most be created
  27. 27. SharePoint Hosted Demo
  28. 28. Thank you! Daniel Sörlöv Alexander von Malachowski  Twitter: @sorlov  Twitter: @a_von_m  http://www.powershelltaskforce.com  http://www.powershelltaskforce.com  daniel@sorlov.com  alexander.vonmalachowski@connecta.se  http://sorlov.azurewebsites.net  http://facebook.com/sorlov
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×