280 likes | 427 Views
Getting Started with SharePoint 2013 Apps. Randy Williams, AvePoint USA Steve Sofian, a rvato Systems Singapore. Randy Williams. Evangelist / Architect. Author. @ tweetraw randy.williams@avepoint.com. Steve Sofian. Regional Consulting Manager
E N D
Getting Started with SharePoint 2013 Apps Randy Williams, AvePoint USA Steve Sofian, arvato SystemsSingapore
Randy Williams Evangelist / Architect Author @tweetrawrandy.williams@avepoint.com
Steve Sofian • Regional Consulting Manager • .NET / SharePoint / Business Intelligence • Customer Engagement Platform • Over 15 years of software development and systems integration • Microsoft SharePoint MVP since 2007 • Founder and community lead for Singapore SharePoint Community http://www.facebook.com/groups/sgsharepoint/ • Co-organizer Southeast Asia SharePoint Conference 2010, 2011, 2013 Author
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
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
What is a SharePoint 2013 App? Self-contained pieces of functionality that extend the capabilities of a SharePoint website Microsoft - bit.ly/MFDnI9
Demo Built-in Apps A quick look at what’s built in
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
How apps run OAuth CSOM/OData Other Platform SP Farm
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
Demo Apps Creating our first SharePoint Hosted App
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
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
Demo .app package Let’s take a look inside
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
CSOM • Same object models as before • .NET Managed code • JavaScript • Silverlight • Much richer API compared to 2010
OData • REST-ful API • Virtually same coverage as CSOM
Demo Using OData
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