With SharePoint 2013 just around the corner a plethora of new features for developers will also become available. Starting with enhancements in Visual Studio 2012 for SharePoint developer, iterating through the new SharePoint REST and OData, WCF Data Services framework, Client Side/JavaScript Object Model (CSOM/JSOM), new WCF service for BCS or Remote Event Receivers, ending with building applications for the new tore, we will walk you through you what you need to get your current skillset updated for the SharePoint 2013.

1. Developer Day
What’s new for developers
in SharePoint 15
Valerie Alonso
Marius Constantinescu

2. branding.technology.integration
in brief
• + 300 employees
• headquartered in Geneva
• founded in 1995
• international culture
• multi-national clients
• integrated solutions
• microsoft managed partner

3. Global
Launch
6 NOV 2012

4. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

5. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

6. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

7. 1 billion+
A new class of Apps enabling new
Office scenarios and User experiences
Users
75% developers using 700k+
HTML 5 & CSS 3 SharePoint
Developers
Public Web API
Deploy & Maintain your Apps publicly or
Flexible internally with Flexibility & Control
Lifecycle
Designed for the Cloud
Give more choices to developers
New
Enable consistent development Toolset
platform

8.  Farm solutions
 Sandbox Solutions
 Client Side solutions
 Common issues

9.  One web-based model
available across
Office & SharePoint
 An App is an
autonomous Web
Application extending
SharePoint
functionalities
 Communicates with
internal and external
Services using
industry standards
(REST/OData, JSON)
 Flexible
authentication flow via
OAuth2
 Flexible hosting and
deployment model

11. demo

12. Use Apps whenever you can
•Enforce better architectural approaches, such as 3-tier architectures
•Remember that you are limited to CSOM and REST API
•Targeting specific scenarios
•Use SharePoint hosted for standalone reusable components
•Use Cloud hosted for Large corporate business applications
•Use Cloud Hosted or Azure Auto-hosted for wide-reach and public marketplace
Use Apps to take away code from Server, better upgrade stories & no-customized environment
•Administrative extensions (Timer-Jobs, Application Services, PowerShell extensions)
•Extend SharePoint functionalities
Use solutions (Farm or Sandbox) for SharePoint deep-integrated development
On-premises Custom Web Parts, Application Pages, Custom web services, Event receivers & Feature receivers
•Custom field (column) types
•Not supported
•Custom site definitions, Delegate controls, Custom themes, Custom action groups and custom action hiding
•User controls (.ascx files)

13. Developer
Information Worker
IT Manager
Administrator

14. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

16. Area REST / CSOM (Script & Client
REST / OData Namespace)
•https://sharepoint.b-i.com/_api/web/Title Web  http://weburl/_api/Web
 SP
 Microsoft.SharePoint.Client
Managed Code
Search  http://weburl/_api/Search
•ClientContext ctx = new ClientContext("https://sharepoint.b-i.com");  SP.Search
•ctx.Load(ctx.Web.Title);  Microsoft.SharePoint.Client.Search
•ctx.ExecuteQuery();
Taxonomy  http://weburl/_api/Taxonomy
 SP.Taxonomy
 Microsoft.SharePoint.Client.Taxonomy
JavaScript
•var ctx = new SP.ClientContext("https://sharepoint.b-i.com"); Social  http://weburl/_api/Social
ctx.load(ctx.get_web().get_title());  SP.Social
ctx.executeQueryAsync();  Microsoft.SharePoint.Client.Social

18. SSOM Server Side Object Model
• Windows PowerShell command, Timer job
• Central Administration Extensions, Application Pages, Web Part or User Controls
• SharePoint Farm-wide consistent branding
CSOM Client-Side Object Model
• .NET Console, Web Role or Worker Role in Azure, Server external to SharePoint to perform CRUD operations (non-phone applications)
• ASP.NET Web Application CRUD on SharePoint or BCS Lists (not behind a firewall)
• WCF Data Services with LINQ (target either listdata.svc for list-based operations or client.svc to access other entities)
JSOM JavaScript Object Model
• CRUD Operations on SharePoint Data (batch operations and asynchronous calls)
• ASP.NET Web Application CRUD on SharePoint or BCS Lists (across firewalls)
• Data always returned in JavaScript Object Notation (JSON)
Mobile Mobile Client Object Model
• Windows Phone Application with CRUD on SharePoint Data (core functionality only)
• Special extension to support Push Notification Service to alert mobile devices on events (could be combine with Remote Event Receivers)
• Use REST/Odata for all other non-core extensibility points

19. App Server
Push Notifications

20. What is it STS (ACS) 7
3
6
2
1
9
4 8
Why SharePoint Server
5
10
Browser App.com
Other

21. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

22. Office 365 Web App “Napa”
Visual Studio 2012
SharePoint Tools
SharePoint Designer 2013
SharePoint built-in tools
 Developer Dashboard
 SharePoint Design Manager

23. demo

24. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

25. What is it
• Business Connectivity Services (BCS), in SharePoint 2010 was an improvement to the Business Data
Catalog (BDC) created for Office SharePoint Server 2007.
• BCS enables SharePoint to access data from external data systems or LOB Systems (such as SAP, ERP, CRM)
• Other data-driven applications that are exposed through Windows Communication Foundation (WCF)
services endpoints or .NET Assemblies
What’s new
• Enhanced support for REST & CSOM
• Connectivity to OData sources
• Application Scoped External Content Types
• Notification Callbacks via External Events

26. Extensibility Office 2010/2013
Rich-Client Integration
Authoring Tools Presentation Outlook Integration
External Lists SharePoint Object Model Contacts OData
Calendar
Tasks • Automatic generation of BDC Models based on OData Sources (via
External Columns REST API
Discussion Lists
Visual Studio 2012)
• REST API available for ECTs opening for Web and Mobile development
CSOM API
Event Listener
Word
App-Scoped External Content Remote Event Receivers • Event subscribers receive notifications from publishers (external systems
Visual Studio
Types
– must implement interfaces!) via “Push notifications” (post to REST end-
2012 SharePoint Enterprise point specified) or Code Callouts hooks
• 2 new Events receiver operations - Subscribe/Unsubscribe
Rich-Client Extensions • Supported connections (OData, WCF, SQL) and data payload returned as
ATOM or JSON
External Content Types • Subscription enable event receivers on External lists - (events triggered
SharePoint Business Data Web Parts on data change for target Entity are shipped as Alerts on Views
Designer 2013
App-Scoped External Content types
• BDC Models packaged in a SharePoint App – scoped only to that App
Profile Pages
• Connections could be either built-in the BDC Model or in the BCS
Connection Settings object - shareable (requires Secure Store)
• Only works with OData sources
External Data Search
SQL WCF .NET OData
Database Service Assembly Sources
Secure Store
SharePoint Connector Framework

27. Cloud-App model Web standards Core Platform Developer Tools BCS Workflow
Content Social & Application
Search Mobility Management Collaboration Services

28. Azure Access Control
Workflow Manager 1.0
OAuth2
Authoring Tools Office 365 / SharePoint 2013 • Hosts WCF and WF 4.0
• Client/Server rely on
Solution Packages Content SharePoint 2010
Workflow Host
OAuth for secure
SharePoint Apps Events (WF v3)
Visual Studio Azure Workflow
communication
2012
SharePoint Object Model
Workflow Services Manager
Deployment Interop
REST
Workflow Services
SharePoint
Designer 2013 Instances Messaging
Routed
Events Manager
Azure Service Bus
Events
• Control workflow
Visio Pro 2013
Azure Workflow
Service Application Proxy execution

29.  Visio 2013 Authoring
Improvements Be more efficient when authoring your workflows
• C# Expressions
• Designer Improvements – totally create workflows declaratively via
 SharePoint Designer 2013 • State Machine, Contract-First
 Core Actions
Versioning Basic building blocks to enable building a
versioning story
• Workflow Identity – traceable, persistent & query-able association information between
 Coordination Actions Instance and Definition
• Side by Side Versioning
• Dynamic Update
 Project Actions
 Visual Studio 2012 Runtime
Enhancements Improve runtime performance and extensibility
• Improved performance on VB Expressions
• Expressions Extensibility
• Partial Trust (run from within a SharePoint App)

30. Cloud-App model Web standards Core Platform Developer Tools BCS Workflows
Content Social & Application
Search Mobility Management Collaboration Services

31. Les Apps, nouveauté SharePoint 2013
15:15 Berlin
Gestion de contenu web avec SharePoint
2013
16:30 Berlin
Office Client 2013: Nouvelles fonctionnalités
et principe d’application
16:30 Albertville

32. Thank you