Getting Started withSP2013 AppsRandy WilliamsEnterprise Trainer and EvangelistAvePoint
Randy Williams            Enterprise Trainer & Evangelist            Based in San Diego, CA            SharePoint MVP f...
Why do we needa new app model
Challenges with WSP solutions Full-trust solutions Sandboxed solutions Requires administrative deployment and support ...
Benefits of the new app model                  • Based on a proven and familiar app model                  • Apps can be f...
What is a SharePoint 2013 App?  Self-contained pieces offunctionality that extend thecapabilities of a SharePoint         ...
Demo       Built-in Apps
Um, as a dev - what exactly is an app?                               An application whose interface is                    ...
How apps run
What SharePoint artifacts are supported? *   Modules: pages, js libraries, images, other file-based resources   Custom a...
Demo       Apps
Apps vs solution packages                                        Apps        Sandboxed WSP      Full trust WSP            ...
Three hosting options
Three hosting options
Three hosting options
Three hosting options
Host web and app web The host web is where app is added, removed, upgraded If app has SharePoint artifacts, a sub-web is...
App web Provisioned by host web Contains only web-scoped features Initial UI is immersive, full page Custom master pag...
Demo       .app package
API Support (_api) Remote APIs are now a first-class citizen Client-side object model (CSOM) REST-based (OData) OAuth
CSOM
CSOM Same object models as before Much richer API compared to 2010
OData
OData REST-ful API Virtually same coverage as CSOM
Demo       Using OData
Bonus Demo (if time permits)                           Apps
How do I get started? Sign up for Office 2013 developer site     http://dev.office.com Get Visual Studio 2012     http:/...
Thank you
Upcoming SlideShare
Loading in...5
×

Getting Started with SharePoint 2013 Apps

2,808

Published on

The latest release of Microsoft SharePoint is primed to change the rules when it comes to building applications. In this session, come get a demo-centric introduction to what's new and improved. We'll cover what "off box" really means and how these external apps integrate with SharePoint. We'll look out the different hosting options to help you decide where you app should run, and introduce the new client APIs as well as discuss authentication mechanisms within your solutions. We’ll also explore changes in deployment packaging options – it’s an exciting new world for developers, come join us and take the first step into the future.

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

No Downloads
Views
Total Views
2,808
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide
  • The latest release of Microsoft SharePoint is primed to change the rules when it comes to building applications. In this session, come get a demo-centric introduction to what's new and improved. We'll cover what "off box" really means and how these external apps integrate with SharePoint. We'll look out the different hosting options to help you decide where you app should run, and introduce the new client APIs as well as discuss authentication mechanisms within your solutions. We’ll also explore changes in deployment packaging options – it’s an exciting new world for developers, come join us and take the first step into the future.
  • Getting Started with SharePoint 2013 Apps

    1. 1. Getting Started withSP2013 AppsRandy WilliamsEnterprise Trainer and EvangelistAvePoint
    2. 2. Randy Williams  Enterprise Trainer & Evangelist  Based in San Diego, CA  SharePoint MVP for 2009, 2010, 2011  Speaker at many global conferences 20+ years in IT Columnist: SharePoint Pro magazine randy.williams@avepoint.com @tweetraw
    3. 3. Why do we needa new app model
    4. 4. Challenges with WSP solutions Full-trust solutions Sandboxed solutions Requires administrative deployment and support Lifecycle management Steep learning curve Not cloud ready
    5. 5. Benefits of the new app model • Based on a proven and familiar app model • Apps can be found in SharePoint Store or a corporate app catalog Info Workers • Can provision, upgrade and delete • Lower learning curve – re-use your existing web technology background • SharePoint Store opens up new revenue potential Developers • Apps decoupled from SharePoint – simplifies upgrades • Virtually no risk to farm • Corporate catalog facilitates governance controls IT Managers
    6. 6. What is a SharePoint 2013 App? Self-contained pieces offunctionality that extend thecapabilities of a SharePoint website
    7. 7. Demo Built-in Apps
    8. 8. Um, as a dev - what exactly is an app? An application whose interface is surfaced through SharePoint but code is executed elsewhere Can contain some declarative SharePoint artifacts External app provides SharePoint UI through IFrame External app uses CSOM or REST (OData) calls to call back No custom server-side code running on SharePoint
    9. 9. How apps run
    10. 10. What SharePoint artifacts are supported? * Modules: pages, js libraries, images, other file-based resources Custom actions: ribbon or ECB Client web part (“app part”) List instances, columns, content types Remote event receivers * SPWeb-scoped features only When adding an app, a sub-web is created to hold these artifacts; when removing an app, sub-web is deleted
    11. 11. Demo Apps
    12. 12. Apps vs solution packages Apps Sandboxed WSP Full trust WSP Anywhere but Farm (User CodeWhere does server-side code run? Farm (w3wp.exe) farm Service)Scalable Highly Limited Based on farm Site collectionWho installs and removes Users Farm admin adminSupported in SP2013 Yes Yes YesSharePoint Online compatible Yes Yes NoAzure-hosting compatible Yes No NoRequires local farm for developers No Yes YesRemote deployment and debugging Yes No Nofrom Visual Studio
    13. 13. Three hosting options
    14. 14. Three hosting options
    15. 15. Three hosting options
    16. 16. Three hosting options
    17. 17. Host web and app web The host web is where app is added, removed, upgraded If app has SharePoint artifacts, a sub-web is created underneath the host web This sub-web is called the app web App web is only accessible using isolated domain name
    18. 18. App web Provisioned by host web Contains only web-scoped features Initial UI is immersive, full page Custom master page is assigned (app.master) Quick launch and common layout pages are unavailable Only declarative code allowed
    19. 19. Demo .app package
    20. 20. API Support (_api) Remote APIs are now a first-class citizen Client-side object model (CSOM) REST-based (OData) OAuth
    21. 21. CSOM
    22. 22. CSOM Same object models as before Much richer API compared to 2010
    23. 23. OData
    24. 24. OData REST-ful API Virtually same coverage as CSOM
    25. 25. Demo Using OData
    26. 26. Bonus Demo (if time permits) Apps
    27. 27. How do I get started? Sign up for Office 2013 developer site http://dev.office.com Get Visual Studio 2012 http://www.microsoft.com/visualstudio/eng/downloads Download the Office Developer Tools for Visual Studio 2013 RTM - Preview http://go.microsoft.com/fwlink/?LinkID=261869
    28. 28. Thank you

    ×