SEASPC-Getting Started with SP2013 Apps - Engage

warbarnacleSecurity

Nov 5, 2013 (4 years and 2 days ago)

70 views

Getting Started with SharePoint
2013 Apps

Randy Williams, AvePoint

USA

Steve Sofian,
a
rvato Systems

Singapore

Randy Williams


Evangelist / Architect

Author

Steve
Sofian


Regional Consulting Manager


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

Why do we need
a new app model

Challenges with WSP solutions


Full
-
trust solutions


Sandboxed solutions


Requires administrative deployment and support


Lifecycle management


Steep learning curve


Not cloud ready

Benefits of the new app model


Lower learning curve


re
-
use your existing web
technology background


SharePoint Store opens up new revenue
potential

Developers

IT Managers


Apps decoupled
from SharePoint


simplifies upgrades


Virtually no risk to farm


Corporate catalog facilitates governance controls

Info Workers


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

Self
-
contained
pieces of
functionality that extend the
capabilities of a SharePoint
website

What is a SharePoint 2013 App?

Demo

Built
-
in Apps

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

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

Apps
vs

solution packages

Apps

Sandboxed WSP

Full trust WSP

Where does server
-
side code run?

Anywhere

but
farm

Farm (User Code
Service)

Farm (w3wp.exe)

Scalable

Highly

Limited

Based on farm

Who

installs and removes

Users

Site collection admin

Farm admin

Supported

in SP2013

Yes

Yes

Yes

SharePoint Online compatible

Yes

Yes

No

Azure
-
hosting compatible

Yes

No

No

Requires local farm

for developers

No

Yes

Yes

Remote deployment and debugging from
Visual Studio

Yes

No

No

Three hosting options

Three hosting options

Three hosting options

Three hosting options

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




App web


Provisioned by host web


Contains only web
-
scoped features


Initial UI is immersive, full page


Custom master page is assigned (
app.master
)


Quick launch and common layout pages are unavailable


Only declarative code allowed


Demo

.app package

API Support (_
api
)


Remote APIs are now a first
-
class citizen


Client
-
side object model (CSOM)


REST
-
based (OData)


OAuth



CSOM

CSOM


Same object models as before


Much richer API compared to 2010

OData

OData


REST
-
ful

API


Virtually same coverage as CSOM


Demo

Using OData

How do I get started?


Sign up for Office 2013 d
eveloper 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

Thank you to our sponsors

29