SPCA2013 - Once you go app you don't go back
Upcoming SlideShare
Loading in...5
×
 

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

on

  • 308 views

Once you go app you don't go back

Once you go app you don't go back

Statistics

Views

Total Views
308
Views on SlideShare
308
Embed Views
0

Actions

Likes
0
Downloads
14
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

    • §
    • 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 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 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
    • 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 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 _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 Service must be started  App catalog most be created
    • SharePoint Hosted Demo
    • 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