Tag: Jumpstart

Inside Apps for Office and SharePoint – Jumpstart 2012

We recently attended the excellent Jumpstart for Apps for SharePoint & Office at Microsoft in Bellevue. The event was designed to (and accomplished it’s goals) to be a bit of a boot camp for the huge push towards the App model Microsoft has adopted. Here’s the presentations with my take on things.

Jumpstart Introduction

An overview of the two day event agenda and primer on the Apps model. Some key take aways:
– Biggest shift in strategy since Office ’97 intro of VBA
– Goal is to overcome trust issues with stability of apps
– Embedability is key goal e.g. LinkedIn widget embedded in an Outlook App Pane

0-60 on Apps for Office Dev

– Apps for Office Tech Intro
– Doc Centric apps (Word, Excel, PowerPoint, Project)
– Outlook / Outlook Web Access Apps
– App defined as an Iframe inside Office
– Deployment Locations : Marketplace | SharePoint | Network Share

Setup Environment
○ Office 365 dev tenant (napa)
○ VS with Office Tools

Code App
○ Office.js for clientside UI

○ Register
○ Host
○ Marketplace

○ No ActiveX or Silverlight (?!)
○ Same origin policy

App Types
○ Content
○ Task Pane
○ Mailbox

Task Pane Apps
– Appear in Outlook/OWA Only
– Contextual
– Use Mailbox APIs
– Manifest installed to Exchange
– Outlook processes rules
– Activation Rule Types
– Regexps can be used to parse mails e.g. UPS tracking #
– Max of 10 rules per manifest

Exchange Entities
– Exchange detects specific entities

Persisting Data
– Per-App Property Bag | Per-App & Per-Item Property Bag
– 32KB limit

Building Apps for SharePoint

Duration User Limit
Free Perpetual Unlimited
Trial 30d, 60d, 120d, unlimited N per user / unlimited
Paid Perpetual N per user / unlimited
Subscription Monthly or Yearly N per user / unlimited

This is an embedded Microsoft Office presentation, powered by Office Web Apps.

Apps for Office UX

This is an embedded Microsoft Office presentation, powered by Office Web Apps.

SharePoint APIs and App Security

2010 Model > _vti_bin/client.svc focus

Web http://weburl/_api/web
Search http://weburl/_api/Search
Taxonomy http://weburl/_api/Taxonomy
BCS http://weburl/_api/BCS

SharePoint Connect = Booyah

Auth chain = 4 outcomes:
• Use Anonymous Context
• Set App Only Context
• Set App and User Context
• Set User Context

Authorization Logical Model
Apps have identity separate from Users
e.g. Printing app is distinct from user using the Printing app

Access is based on grants
Grants are available to AccessCheck
Grants have scopes & rights
E.g. Printing App has READ right on Picture Library”

AccessCheck makes a description using
Identities (User, Application)
Resource Attributes (ACLs)

> User Only
> App & User
> App Only

This is an embedded Microsoft Office presentation, powered by Office Web Apps.

Patterns in Apps for Office

– Class of apps focus
– Standards
– Lifecycle
– Web dev’s should be able to dev for Office

“Agave” “app for office”

– Office
– SharePoint

– CSS3
– JS
– oAuth
– oData

UI Shapes
– Embedded Content
– Task Pane
– Contextual Pane

Pattern Examples
1. Master/Detail Lookup – Provide reference info from trusted authoritative sources
2. Language Assistance – Assist with use of languages during authoring or consumption experiences
3. Contextual Content & Services – Automatically provide relevant info
4. Visualization – Provide rich visual way to analyze manipulate & interact with data in Office docs
5. Data Import & Enhancement – Getting data & data massage
6. Reference & Research – Provide reference info from trusted authoritative sources
7. Authoring & Publishing – Provide document authoring assistance and/or enable Office content to be easily published to a service
8. Service-powered Content Transformation – Use Office or a service to transform content & publish enhanced version of the original
9. Real Time & Social Data – Access and import real-time data. Search analyze and import social data into Office.
10. Forms & Templates – Form integration and assistance in filling in structured data

Patterns in Apps for SharePoint

As the app developer, you have to know the architecture of your app. After you determine how your app will be distributed in remote and SharePoint platforms, you can decide among the available alternatives for building your app UX. You might ask yourself the following questions:

What can I use if I am creating a cloud-hosted app?
What can I use if I am creating a SharePoint-hosted app? For more information, see Hosting options for apps for SharePoint.
How can I connect my UX to the host web? For more information, see Host webs, app webs, and SharePoint components in SharePoint 2013.


slideshow missing. 🙁 Check this link for similar content

Windows Azure and Apps for Office and SharePoint

– 99.95% monthly SLA if you have two instances of an Azure Service
– Pay as you go
– Azure is IIS on steroids. Partitioned IIS instances.
– You get 10 websites, each site can be scaled up 3 instances

SLA’s: http://www.windowsazure.com/en-us/support/legal/sla/
Publish to TFS: http://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/

• New Identity service = Azure AD

This is an embedded Microsoft Office presentation, powered by Office Web Apps.