The new SharePoint App Model provides different ways of building apps. As a developer you have to choose between development techniques, hosting options and more. This session discusses the architecture, various types of apps, application identity and permissions, and how to build these different types of apps. The session contains demos covering building SharePoint-hosted apps, implementing SharePoint 2013 chrome control, setting the right permissions, and more with Visual Studio 2012.

1. Developing SharePoint 2013 Apps
with Visual Studio 2012
Bram de Jager
SharePoint Architect | Microsoft Certified Solution Master: SharePoint

2. Agenda
Evolution
Apps for SharePoint
Visual Studio Tools
REST & CSOM APIs

3. 1
EVOLUTION

4. Development Evolution
Investment in
Portals & content
2003
 Web Parts
 Site
Definitions
App discovery & management
2007
 LOB
applications
 Custom
server side
code
 WSP
deployment
2010




Silverlight
CSOM limited
Sandbox
Web Template
2013
 Apps
 Client side
experience
 CSOM
 REST/oData

5. Customization Options
Farm





Full trust solutions
Customizations to
file system of
servers
Hosted in same
process as
SharePoint
Server side
SharePoint API
access
Classic model from
2007
Sandbox



Hosted in isolated
process
Limited server side
SharePoint API
access
No external service
calls

SharePoint Apps




Deprecated in
SharePoint
2013

New Apps model
Deployed from
corporate catalog or
Office Store
Manage permission
and licenses
specifically
Simple install and
upgrade process
Preferred option

6. “
Note that code-based sandboxed
solutions are still supported in
SharePoint Online 2013 but, no
further investments in that
infrastructure are planned. We
recommend you consider the
Cloud App Model (CAM) as an
alternative.
“

7. App Development Scenarios
Deployment Options
Customization Options
On-Premise Farm
Installation
Farm-Trust Solutions
Web Browser
SharePoint Online
(Office 365)
Sandboxed Solutions
SharePoint Designer
Hosted Installation
SharePoint-Hosted
app
Visual Studio
Provider-Hosted app
Eclipse, etc
Autohosted app
Development Tools

8. 2
APPS FOR SHAREPOINT

9. App Shapes
Full page
Implement complete app experiences to satisfy business
scenarios
App Parts
Create app parts that can interact with the SharePoint
experience
UI command extensions
Add new commands to the ribbon and item menus

10. Hosting Options
Provider-hosted app
Provide your own hosting environment
SharePoint
Host Web
Your Hosted Site
(IIS)
Cloud-hosted apps
- Use server code
- Receive SP events
- Use OAuth to access
SP
Autohosted app
Windows Azure + SQL Azure provisioned
automatically as apps are installed
SharePoint
Host Web
Azure
SharePoint-Hosted app
Provisions an isolated sub web on a host web
- Use SP artifacts & out-of-box web parts
- Use HTML & JavaScript for UI & client-side logic
- Use Workflows for middle tier logic
SharePoint
Host Web
SharePoint
App Web

11. 3
VISUAL STUDIO TOOLS

12. Visual Studio SharePoint Tools
• Development Environments
• Develop against a local SharePoint server
• Remote development against SharePoint Online (Office 365)
• Tools
• Office Developer Tools
• Download http://dev.office.com

13. Debug your app
• No app registration required
• SharePoint Developer Site
• ClientId & ClientSecret are generated for you
• IISExpress is used to host Web project
• ~remoteAppUrl token update so it points to IISExpress Url
(http://localhost:1234)
• LocalDB is used for SQL database
• Connection string updated in web.config from SQL project
• Local workflow service is started & configured

14. Publish your app
• SharePoint-hosted & Autohosted
• No app registration required
• Everything included in the .app package
• Provider-hosted
• Developer must acquire ClientId & ClientSecret via Seller Dashboard (Office
Store only)
• SharePoint artifacts in .app package
• Web assets in Web Deploy package - developer must deploy
• Developer must publish & deploy SQL assets if not in Web Deploy package

15. Anatomy of an App Package
App Web
WS
P
.app Package
(OPC)
Host
Web
(from WSP)
Azure

16. “
DEMO
Building your first app
“

17. Demo Silly Facts
• SharePoint-Hosted app
• Look around
• AppManifest.xml
• SharePoint Artifacts
• Silly Fact content type and Facts list
• App Part (Client Web Part)
• Custom Action (Host web)

18. 4
REST & CSOM

19. Changes from 2010 to 2013
• The client.svc service extended with REST capabilities
• client.svc now supports direct access from REST clients
• client.svc accepts HTTP GET, PUT, POST requests
• Implemented in accordance with OData protocol
• CSOM Extended new APIs
• Focus investment on SharePoint Server APIs
• Search, Social, Taxonomy, Workflow, Analytics, Sharing, Publish
ing, eDiscovery, IRM, BCS, … and more

20. SharePoint 2013 Remote API
_api is new alias for _vti_bin/client.svc
Server
Client
REST
OData
JSON
CSOM
JavaScript
Library
Silverlight
Library
Custom Client Code
.Net CLR
Library

21. Why is REST Important?
• Significant Industry Momentum
• Simple and Easy to Use
• Much easier to use than SOAP-based Web service
• Higher productivity when using JavaScript and jQuery
• Results can be returned in JSON and ATOM format
• Test in a browser
• Platform agnostic
• Each query is submitted with a unique URL
• Results can be cached by proxy servers

22. REST URLs in SharePoint 2013
• CSOM URLS can go through _api folder
• Simplifies URLs that need to be built
• Removes client.svc file name from URL
• You can replace this URL
• http://contoso.com/_vti_bin/client.svc/web
• With this URL
• http://contoso.com/_api/web

23. Mapping Objects to Resources
• Example REST URLs targeting SharePoint
• _api/web/lists
• _api/web/lists/getByTitle('Announcements')
• _api/web/getAvailableWebTemplates(lcid=1033)

24. App Authentication
• Use OAuth for secure communications
• SharePoint & web application (IIS) trust third party (ACS)
• Trust developed using ClientId & ClientSecret
• SharePoint & ACS know the ClientId
• Web application & ACS know the ClientSecret

25. Online authentication

26. “
DEMO
Using CSOM and
REST
“

27. Demo CSOM and REST
• Provider-Hosted app
• Add web project
• Chrome
• Use CSOM and REST to create silly facts
• User Profile (REST)
• Search (REST)
• Taxonomy (CSOM)

28. 5
WRAP-UP

29. Summary
• The way forward for customizations on SharePoint
• Build for the cloud (Office 365)
• Heavily invested in CSOM and REST, allowing interaction with
SharePoint

30. Try it yourself
• Office Store
• Play around with current Apps for SharePoint
• Office 365 playground
• Sign up on http://dev.office.com for Office 365 playground
• SharePoint Client Browser
• http://spcb.codeplex.com

31. “
Questions & Answers
Thank You!
“

32. Bram de Jager
bram.de.jager@macaw.nl | bramdejager.wordpress.com |
@bramdejager