SharePoint Apps are the new way to create applications in SharePoint 2013. SharePoint Apps are the intended replacement for Sandbox Solutions. These work well both in on-premise and cloud SharePoint installations.

1. SACRAMENTO

2. SharePoint Apps in SharePoint
2013
Ryan Schouten
@shrpntknight
ITG

4. About Me
Ryan Schouten
Worked with SharePoint for 7 years
I have experience with SharePoint 2003 – 2013
I have worked with ASP.Net for 11 years
MCPD
Contact Information
Ryan.Schouten@itg-mail.com
@shrpntknight
http://www.sharepointknight.com

5. Objectives
• The Need
• Benefits
• Hosting Options
• Limitations
• New Functionality
• Development Options
• Permissions and Security
• Deployment
• Break it Down

6. Why the change

7. Hence the new App Model
• No custom code on the SharePoint server
• Easier to upgrade to future versions of SharePoint
• Works in Office 365 SharePoint Online without limitations
• Reduces the ramp-up time for those building apps
• Don’t need to know/be as familiar with SharePoint “-isms”
• Leverage hosting platform features in new apps
• Enables taking SharePoint apps to different levels – further than what
can be done with farm / sandbox solutions

8. Benefits (continued)
• Low cost of entry for developers
• Hosted SharePoint Dev sites
• No need to have a farm per developer (Shared Development Farms/Tenants)
• No Intensive development environment requirements

9. Hosting Options
SharePoint-Hosted App
Provision an isolated sub web on a parent web (separate domain)
• Reuse web elements
(lists, files, out-of-box web parts)
• No server code allowed; use client JavaScript for logic, UX
Provider-Hosted App
“Bring your own server hosting
infrastructure and technology platform”
Get remote events from
SharePoint
Use CSOM/REST +
OAuth to work with SP
Cloud-based Apps
Your
Hosted Site
Autohosted App
Windows Azure + SQL Azure provisioned
invisibly as apps are installed
Azure
SharePoint
Host Web
App Web*
(separate SharePoint
domain)
SharePoint
Host Web
App Web*
(separate SharePoint
domain)
SharePoint
Host Web
App Web
(separate SharePoint
domain)

10. Hosting Comparison
SharePoint Hosted Cloud Hosted
App Scope SharePoint Site Site or Tenancy
Architecture Web Site Can be Multi-Tenant
App
Developer Skillset SharePoint + HTML/JS Full Stack
UI Technologies SharePoint + HTML/JS Any Web Stack
Server Code None Any
Storage Lists and Libraries Any
Key Limitations No Server Code Hosting Expertise
Required
Good for… Smaller apps &
resource storage
Any type of Application

11. App Presentation Options
Shape Description Example
Immersive Full Page App App that implements a
new scenario for
customers
Resource Tracking,
Budgeting
App Part Provides new parts you
can add to your sites
Weather, News, Stock
Ticker
Extension App Add new actions for
documents and items
Display Document
Visualization, Print to
Print Service Vendor

12. Limitations
• Apps in general
• Deployed to different domain(extra login possible)
• Initial configuration is a pain
• App Parts
• Loaded in an iframe(size is fixed)
• Also loaded from other domain

13. New Functionality
• Improved CSOM
• Improved Rest API
• Needed since code is not run in SharePoint Processes
• O-Auth Security
• New Security Model to allow app specific permissions

14. Let’s Create Our First App

15. JSOM Library
• Library has two versions
• PS.js – minified version of the library
• PS.Debug.js – unminified with intellisense
• Both can be found in the layouts folder
• %ProgramFiles%Common FilesMicrosoft SharedWeb Server
Extensions15TEMPLATELAYOUTS
• http://siteurl/_layouts/15
• Easiest way to reference it in SharePoint is
<SharePoint:ScriptLink name="PS.js" runat="server" ondemand="false" localizable="false" loadafterui="true" />

16. Example
SP.SOD.executeOrDelayUntilScriptLoaded(GetProjects, "PS.js");
function GetProjects()
{
var projContext = PS.ProjectContext.get_current();
projects = projContext.get_projects();
projContext.load(projects, 'Include(Name, CreatedDate, Id)');
projContext.executeQueryAsync(onQuerySucceeded, onQueryFailed);
}

17. Continued
function onQuerySucceeded(sender, args)
{
var projectEnumerator = projects.getEnumerator();
while (projectEnumerator.moveNext()) {
var project = projectEnumerator.get_current();
var row = tblProjects.insertRow();
row.insertCell().innerText = project.get_name();
row.insertCell().innerText = project.get_createdDate();
row.insertCell().innerText = project.get_id();
}
}

18. Let’s Try It

19. Permissions and Security
• Apps have their own permissions
• You must specify what SharePoint you want to access in your
Manifest
• Content is secured through Oauth
• Users must have the permissions you need for them to install

20. Deployment
• Everything Packaged into a .app file
• This can be used to add the app manually to a site or publish it to the
SharePoint Store

21. Let’s Examine How this works

22. Gotchas
• On-Premise Sites are not configured by default to handle Apps
• Sideloading of apps is not enabled on this site.
• Enable-SPFeature e374875e-06b6-11e0-b0fa-57f5dfd72085 –
url http://sp.contoso.com
• App Management Shared Service Proxy is not installed.
• Technet article on how to setup On-Premise for development
• http://msdn.microsoft.com/en-us/library/fp179923.aspx

24. Join us right after at The Blue Prynt
Socialize and unwind after our day of learning.
Blue Prynt Restaurant & Bar
815 11th St, Sacramento, CA 95814
bluepryntsacramento.com
SACRAMENTO