What’s new in SharePoint 2013 for devsChris O’Brien SharePoint MVPwww.sharepointnutsandbolts.com

Agenda (TODO)

.NET 4.5?Tooling

List/ctype designerGeneric VS improvements?

IntelliTrace?

AppsSP-hostedCloud-apps

Provider-hostedAuto-hosted (Azure)

Client-side rendering

Search/CSWP

Cross-site publishing/metadata-based navigation

Apps for Office

Tooling

Visual Studio 2012 enhancements

SearchSharePoint IntelliTraceBetter testing

List/content type designer

Apps - what is an app?

Adds some specific functionality to a siteE.g. expense reporting, time-tracking etc.

Apps should be safeA bug/performance issue cannot affect the overall stability of SharePointThe ‘engine’ may be in the cloud or on a non-SP server

Apps can be obtained from the app store (“SharePoint Store”)

Apps - Customising SharePoint – official guidance

Microsoft:

The most important guidance we can give you is to develop an app for SharePoint rather than a classic solution whenever you can.

http://msdn.microsoft.com/en-us/library/jj163114(office.15).aspx

Apps - hosting options

SharePoint-hostedJavaScript only

Cloud appProvider-hosted (YOU deal with hosting)

IIS, PHP/LAMP, something else!

Auto-hosted (O365 + Azure)E.g. automatically create database in SQL Azure

Hybrid app = combination

3 questions to answer

Are we going to allow apps?Create infrastructure, obtain wildcard SSL certificate etc.

Are we going to allow ANY app from the SharePoint Store to be installed?

Or are we going to restrict to certain ‘approved’ apps via the internal App Catalog?

Will our own customisations be developed as apps?

demo

Apps (and tooling)

Display Templates (aka JSLink)

Use JavaScript to customise appearance of:Web partsItems in a SharePoint listSearch resultsContent Search Web PartAdding/editing a list itemViews on a listSpecific fields on a list

Specify your JS file with JSLink propertyOOTB Display Templates stored in Master Page Gallery

Web partSpecifies the query and templates to useTriggers templates when search results are available

Logical Model of Display Templates

Control Template (Begins)Determines how to lay the items out on the pageRendered once per web part on the pageItem TemplateDetermines how each item should lookRendered sequentially, once per search result item

Control Template (Ends)After all items rendered, control template finishes rendering

demo

Display templates

Managed Navigation

No longer just based on sub-sites

Site structure/IA not defined by navigation needs

Friendly URLs (no “/Pages/”)

Cross-site publishing

Same information, showing in multiple places

Break through site collection barrier

Good for authoring/publishing and multi-lingual

Closing thoughts

AppsThe Store could be a great thing for SharePointDeveloping: what benefits is the app framework providing?Learning curve to app development

Greater prevalence of ‘classic’ web dev technologies

Several end-user and dev constraints removedSite collection boundaryNavigation based on site structure

Mail: chriso_brien@hotmail.com

Blog: www.sharepointnutsandbolts.com

Twitter: @ChrisO_Brien

LinkedIn: http://uk.linkedin.com/in/chrisobrienmvp

Follow-up questions?

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS

PRESENTATION.