Enabling Developers with

Development FeaturesPresented by: Ricardo Wilkins

SharePoint Solutions Architect

Discussion Points

Today’s SharePoint vs Old Stuff

Apps & the App StoreTools & Deployment

OptionsCoding Walkthru

SharePoint Portal Server 2001

SPS 2003MOSS 2007

SharePoint Server 2010

SharePoint Team

Services 1.0

Windows SharePoint Services

(WSS) 2.0

WSS 3.0SharePoint Foundatio

n 2010

SharePoint Server 2013

SharePoint Foundatio

n 2013

Evolution

App model

Dev Tools

Deployment Options

What’s New

Bottom Line:

Client-side is the future

No more excuses

Features | Solutions | Apps

Features • Used to deploy artifacts• List templates, workflows, web parts, etc

Solutions • Used to deploy code & files• Usually includes Feature(s)• Package of files (*.wsp)

Apps • New in SP2013• Used to deploy solutions & other things

that make up an App• Package of files (*.app)

Farm | Sandbox | SP Apps

Farm

• Full trust solutions

• Full access API• Classic model

from 2007• On-premise

only

Sandbox

• Declarative elements

• Partially trusted code service still included for limited server side support

• Resource monitored

• SPO friendly

SP Apps

• New Apps model

• Deployed from corporate catalog or office market place

• Manage permission and licenses specifically

• Preferred option

7

No custom code on the SharePoint serverEasier to upgrade to future versions of SharePoint

Works in hosted environments w/o limitations

Reduces the ramp-up time for those building appsDon’t need to know/be as familiar with SharePoint “-isms”

Leverage hosting platform options in new apps

App Model Benefits

8

Why Apps?

End Users: consumerization thru app catalogs

IT Pro: stable SP environments

Devs: reuse existing skill sets

Why Apps?

Easy discovery, purchase and installation process for UsersSafest way for admins to extend SharePointSimple marketing and sales system for app revenueMaximize flexibility in developing future upgradesMaximize your ability to leverage non-SharePoint skillsSmoother integration with cloud-based resourcesPermissions distinct from the userCross-platform standards (REST, OData, OAuth, etc)Cross-domain access via Javascript and proper security

mechanismsWork as well online as on-premise

10

Tools

Visual Studio

Client-side Object Model

• Client-side OM greatly expanded• Search• Taxonomy• Feeds• Publishing• Sharing• Workflow• IRM• Analytics• E-Discovery• Business Connectivity Services• Mobile

Napa

Deployment Options

SharePoint-hosted

Cloud-hostedProvider-hostedAzure Auto-hosted

Apps – Possible scenarios

16

Apps – Possible scenarios

16

17

Apps – Possible scenarios

17

18

Apps – Possible scenarios

18

19

App Store | App Catalog | App Market

20

App Store | App Catalog | App Market

Analysis

Architects importantAdditional configuration (security)Code Scope (App Web)Data Access Performance (Farm vs Apps; network & cloud

latency)Full screen apps vs chromeIsolationApps and Search Crawl (not by default)Access external web services & databases (unlike Sandbox

solutions)Non-.NET participationNo upgrade concerns – really?Process monitoring (no longer needed?)IT Pro headaches a thing of the past?

Demo (by screenshot)

http://msdn.microsoft.com/en-us/library/office/apps/fp179924.aspx

Demo – Build with ‘Napa’

Seller Dashboard(

http://dev.office.com)

Office and SharePoint Store

In-product App Discovery

Direct SalesNegotiated deals/

IT projectsApp Catalog

TRIAL/ PURCHASE

TRIAL/ LEAD

OFFICE/SHAREPOIN

T

Developer

IT admin

End users

Choice, Control and Flexibility

APP VALIDATION

Questions?Enabling Developers with SharePoint Development

Features

Presented by: Ricardo Wilkinsrwilkins@bennettadelson.com

www.SharePointCowBell.com@ricardo303@spcowbell