1 / 28

Getting Started with SP2013 Apps

Getting Started with SP2013 Apps. Randy Williams Evangelist / Architect AvePoint. Randy Williams. Evangelist / Architect. Author. @ tweetraw randy.williams@avepoint.com. Why do we need a new app model. Challenges with WSP solutions. Full-trust solutions

yardley-shannon
Download Presentation

Getting Started with SP2013 Apps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Getting Started with SP2013 Apps Randy Williams Evangelist / Architect AvePoint

  2. Randy Williams Evangelist / Architect Author @tweetrawrandy.williams@avepoint.com

  3. Why do we need a new app model

  4. Challenges with WSP solutions • Full-trust solutions • Performance and stability concerns • Incompatible with SPOL • Sandboxed solutions • Clunky architecture, too limiting • Requires administrative deployment and support • Lifecycle management • Upgrade, decommission • Steep learning curve • Not cloud ready

  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 • Can provision, upgrade and delete Info Workers Developers • Lower learning curve – re-use your existing web technology background • SharePoint Store opens up new revenue potential • Apps decoupled from SharePoint – simplifies upgrades • Virtually no risk to farm • Corporate catalog facilitates governance controls IT Managers

  6. What is a SharePoint 2013 App? Self-contained pieces of functionality that extend the capabilities of a SharePoint website Microsoft - bit.ly/MFDnI9

  7. Demo Built-in Apps A quick look at what’s built in

  8. So, as a dev - what exactly is an app? • 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 An application whose interface is surfaced through SharePoint but code is executed elsewhere

  9. How apps run OAuth CSOM/OData Other Platform SP Farm

  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. Demo Apps Creating our first SharePoint Hosted App

  12. Apps vs solution packages

  13. Three hosting options

  14. Three hosting options

  15. Three hosting options

  16. Three hosting options

  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 • https://apps-af48d482118ab1.apps.contoso.com/{appName} Host Web App Web

  18. App web • Provisioned by host web • Contains only web-scoped features • Initial UI is immersive, full page • Set in appmanifest.xml • Custom master page is assigned (app.master) • Quick launch and common layout pages are unavailable • Settings.aspx, viewlsts.aspx, etc. • Only declarative code allowed

  19. Demo .app package Let’s take a look inside

  20. API Support (_api) • Remote APIs are now a first-class citizen • Search, MMS, User Profile, BCS, et al • User-centric capabilities (no Central Admin-like support) • Client-side object model (CSOM) • REST-based (OData) • OAuth

  21. CSOM

  22. CSOM • Same object models as before • .NET Managed code • JavaScript • Silverlight • Much richer API compared to 2010

  23. OData

  24. OData • REST-ful API • Virtually same coverage as CSOM

  25. Demo Using OData

  26. Bonus Demo (if time permits) Apps Creating a Provider Hosted app

  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. Thank you randy.williams@avepoint.com @tweetraw Slides: slidesha.re/UDpa4K

More Related