9. Why SharePoint 2013 apps?
• End users => consumerization through app catalogs
• IT Pro => keep SharePoint environment stable
• Developers => reuse existing skills sets
Apps are an alternative deployment but farm solutions might
still be valid
10. Apps – three possible scenarios
Developer-Hosted App
Cloud-based “Bring your own server hosting SharePoint Your Hosted
Apps infrastructure” Web Site
Developers will need to isolate
Get remote tenants
events from
SharePoint Azure Auto-
Use CSOM/REST Provisioned App SharePoint Azure
+ Windows Azure + SQL Azure
OAuth to work provisioned invisibly as apps Web
with SPS are installed
SharePoint-hosted App
Parent
Provision an isolated sub web
on a parent web Web
• Reuse web elements App Web
(lists, files, out-of-box web
parts)
• No server code allowed;
use client JavaScript for
logic, UX
12. Local development
Has to be on Windows Server 2008 R2 (or later)
Memory reqs have gone up – 12 GB RAM seems workable ... But TechNet
recommends 24 GB
Extra configuration needed for app development
Visual Studio 2012
Remote development
Sign up for Office 365 Developer Site
Possible to use NAPA – app for building apps
13. Apps connect to SharePoint using
SharePoint 2013 Client Side Object Model (CSOM)
SharePoint 2013 REST API
Javascript cross-domain library (SP.RequestExecutor.js)
Main investments in 2013
Client.svc is extended with REST capabilities
Easier for javascript and non .NET code
Implemented in accordance with oData protocol
Programming style is largely unchanged
New APIs for SharePoint Server functionality
User Profiles, Search, Taxonomy, Feeds, ....
14. • CSOM URLs can go through _api folder
• Replace
http://sharepoint/_vti_bin/client.svc/web
• With
http://sharepoint/_api/web
• Example REST URLs targeting SharePoint sites
• _api/web/lists
• _api/web/lists/List1
• _api/web/?$select=title,id
• /_api/web/lists/getByTitle('Consultants')/Items
• ....
15. Immersive App - app is shown full screen
with in a separate page
Part - App is shown as a part on the
SharePoint page – similar experience to
web part
UI Custom Actions – possible to make
the App available through ribbon or
menu actions for documents and items
See Apps for SharePoint UX design guidelines
16.
17. Guidance about apps
• Use apps whenever you can
• Use apps for decoupling scenario based business
applications
• SharePoint hosted apps for small reusable standalone applications (stock tickers,
RSS feeds, ...)
• Provider hosted for large corporate business applications (time registration,
budgetting, ...)
• Azure auto-hosted apps for public marketplace large scale applications
• Avoid apps for tight UI and feature integration
• Use farm level solutions for administrative interfaces
20. Custom
Nav
provider
HTML
Sketches
CSS
Dreamweaver, Microsoft Expression, …
SharePoint Designer + Visual Studio
21. SharePoint
HTML
Auto Snippet Channel
Sketches Upload
Convert Gallery settings
CSS
Dreamweaver, Expression, etc…
22. Support the tools and
workflows designers use
Variations & Content
Translation
Search Engine Optimization
Cross Site Publishing
Video & Embedding
Image renditions
Clean Urls
Metadata navigation
23.
24. Friendly URL
http://contoso.com/computers
CONTENT SEARCH WEB PART
TERM STORE
NAVIGATION TAXONOMY
Filter query by
Audio CATEGORY:
Cameras COMPUTERS
Computers
Home appliances
Phones Search
TV and video
Use page
maincategory.aspx
35. Search for Developers
Deprecated or changed
SOAP web service has been deprecated
_layouts/_vti_bin/search.asmx
SQL Query syntax removed
XSLT is replaced with Display Templates
What’s new
CSOM – Microsoft.SharePoint.Client.Search.Query
REST web service - _api/search/
36. Typical search customization
scenarios for core results search webpart
No more XSLT
The Search UI is driven by
Query rules
Display templates
Result types
Result sources
37. Customizing search – Query Rules
Control over query results
Defined via a Condition and
Action
Query rules:
Result Blocks
Promoted Results
Ranked Results
38. Customizing search – Display
Templates that define
HTML templates
how a search result looks
SharePoint auto-generates
the JS version and the HTML
Stored in the master page gallery
Support full debugging
39. Customizing search – Result types
Define what Display Templates will display a search
result based upon a condition
Search service
Site Collection
Site Owners
40. Customizing search – Result
Sources and Federated Locations
Replace Scopes
Extended federation options
Remote SharePoint farms
Exchange
OpenSearch
Definable at
Search Service – search administrator – globally available
Site collection level – site collection admin – available to all
sites in site collection
Site – site owners – this site only
41. Content By Search Web Part
Similar to Content by Query Web Part – but
based on indexed content
Show content cross site collections
Show content cross multiple site collections
New presentation template model for easy
content presentation fine tuning
Content rendered in client side
Provides full control on rendering capabilities
using html templates
Easy editors as web part editors for defining
planned query
42.
43. Write once, run anywhere
Hosting freedom
Re-use logic and assets
Use cloud data
Azure Workflow
44.
45.
46. Azure
Access Control
SharePoint
Solutions Content
WF3 OAuth2
Visual Studio
Host Azure Workflow
Apps Events
Azure
SharePoint OM Workflow
Workflow Services REST Calls
SharePoint Manager
Designer Azure
Deployment Messaging
ServiceBus
Instances Interop
Events
Azure Workflow Service
Application Proxy
animated
Notes de l'éditeur
Visual Studio support for automatically generating BDC metadata models from and oData SourceAls