1. Creating Apps for SharePoint 2013
Presented by Christian Holslin
January 16, 2013

2. Agenda
About Christian Holslin
Industry Paradigm Shift: Apps
Emerging Trends
Technology and Tools
Hosting and Infrastructure
Getting Started Resources
QA & Wrap Up

3. About Christian Holslin
Gig Werks
About Christian Holslin
SharePoint Solutions Architect
13 years IT experience
6 years SharePoint experience
Office 2013 JumpStart attendee
SharePoint Conference 2012 attendee
Holds various MCP certifications
Company began in 2002
Gold Partner since 2002
Field managed since 2004
Microsoft Best Partner in 2010, 2011, 2012
Various other Microsoft Awards and Tech Forum Award Winner 2008
Invited into the Partner Evidence Program for SharePoint 2010 & 2013
Market Focus from 100 seats to 150,000
Headquartered in New York with clients across the United States

4. Industry Paradigm Shift: The App Model
Apps Change the way we Architect Solutions
Focal Point: User Experience
Office and SharePoint use Apps to tackle “micro-problems”
There’s an App for that!

5. Solution Architecture: Then and Now
THEN: Monolithic Solutions
NOW: App Solutions
Reliance on server-side code
Heavy reliance on IT support
Service interruptions during upgrades
Limited tooling
Longer time-to-market
Focus is User Experience
Minimal IT involvement
Transparent upgrades
Plethora of tools
Rapid build and deployment
Server-side code still available for compute-intensive needs

6. The Focus is Placed Squarely on User Experience
When you build an App you build the User Experience first
When we design solutions, we always aim to solve User Experience problems
Apps target the snarky “micro- problems” in day-to-day business
Apps will help us avoid time- consuming, error-prone work- arounds
Apps will lead to increased productivity and make work more fun
Apps target key UX pains
Client-side development improves UX
Apps leverage powerful Office toolkit

7. Upgrades are completely transparent to the user
Lowers IT Burden
Using the client-side APIs for SharePoint and Office removes the need for server-side intervention
Upgrades are completely transparent to the user
Apps can be distributed either through the Office Store or via your Corporate Catalog
Even developers can work exclusively in the browser
No maintenance windows
No upgrade windows
Self-service App distribution
Governed App distribution

8. Micro-tools Tighter Platform Integration Closure of the 80/20 Gap
Emerging Trends
Micro-tools
Tighter Platform Integration
Closure of the 80/20 Gap

9. Closing the Feature Gap
Food for thought…
Blend content between Office and SharePoint
Present on-prem and Cloud resources seamlessly in one interface
Eliminate data entry
Copy, share, and archive
Contextualize
SharePoint does everything I need, except…
If I could just do…
Why can’t I see my tasks in this too?

10. My Development Toolkit
Technology and Tools
My Development Toolkit
The App
Office 2013 & Office 365
Visual Studio 2012

11. My Development Toolkit
SharePoint Server 2013 Apps:
On-prem or in the Cloud
Microsoft provides full online development experience via “Napa”
Preview Release
Windows Server 2012
SharePoint Server 2013
Office 2013 & Office 365
Visual Studio 2012
*Office Developer Tools for Visual Studio 2012
*Web Platform Installer (delivery platform)

12. What Is The App App Manifest XML File
App Manifest File <?xml version="1.0" encoding="utf-8" ?> <App xmlns=" ( ProductID="{5eccee90-1e41-4ecc-af8c-485facb5c188}" Version=" " SharePointMinVersion=" " Name="LocalTheater" > <Properties> <Title>Local Theater</Title> <StartPage> </Properties> <AppPrincipal> <RemoteWebApplication ClientId="ca81d a8-8a60-e02ee79a4a6e" /> </AppPrincipal> </App>
App Manifest
XML File
Created by Visual Studio 2012 and automatically deployed to SharePoint 2013
Tells SharePoint where your App content resides
App Implementation
HTML5, JavaScript, ASP.NET, PHP, Apps can be implemented with any web development language
Cross-Platform is the point

13. Hosting and Infrastructure
Provider-hosted
Autohosted
SharePoint-hosted

14. Apps are Hosted Provider-hosted model You host, or IT hosts
Server-side code in whatever language you want
Autohosted model
Automatically deployed to Azure
Server-side code supported by Azure
SharePoint-hosted model
HTML & JavaScript only
Hosted in a SharePoint app web
No server-side code

15. OAuth is an open authorization protocol, it’s not a security library
Provider-hosted model
Client-side code / cross-domain library
Server-side code w/ OAuth
Autohosted model
Same as provider-hosted
SharePoint-hosted model
HTML & JavaScript
Authorization handled automatically
OAuth is an open authorization protocol, it’s not a security library
Visual Studio creates a TokenHelper
Cross-domain library is implemented in SP.RequestExecutor.js
// Load the js file and continue to the
// success event handler.
$.getScript(scriptbase + "SP.RequestExecutor.js", execCrossDomainRequest);

16. Getting Started Developing Apps for SharePoint 2013
Development Resources
Online Resources

17. Training Recommendations
Using JavaScript Library Code in SharePoint 2013
Using SharePoint 2013 REST endpoints
SharePoint 2013 REST API
SharePoint 2013 Client Library (CSOM)
jQuery
HTML5
HTML5
JavaScript and the SP 2013 object model
SharePoint 2013 Client Library (CSOM)
REST/OData APIs
ASP.NET
jQuery
Cross-domain library (SP.RequestExecutor.js)
OAuth

18. Developer Needs Online Resources Apps for Office and SharePoint
Apps for SharePoint Overview
Sign up for an Office 365 Developer Site
Windows Azure Free Trial
Download Tools
Check Out “Napa”
Web Platform Installer
Workstation or VM
16 GB RAM
Quad-core
Big hard drive (they’re cheap)
Office 365 Developer Account
Download these ISOs from MSDN:
Windows Server 2012
SQL Server 2012
SharePoint Server 2013
Visual Studio 2012
Download Dev Tools
Microsoft Office Developer Tools for Visual Studio 2012

19. QA & Wrap Up