More info on techdays.be

1. Brave New Hybrid World
What SharePoint 2013
Really Means to You
Dan Holme
MVP, SharePoint Server
Microsoft Technologies Analyst & Evangelist
Intelliem

2. Dan Holme
danholme http://tiny.cc/danholmepresentations dan.holme@intelliem.com

7. Ancient History

8. 2006

9. 2007 – 2012: Revolutionary Trends

10. SharePoint 2013

11. This Opening Session
The brave new world of business, IT and the cloud
 Megatrends
 Tipping point for enterprise IT
How Microsoft has adapted
SharePoint 2013
What it means for Business, IT and Developers

13. Three Worlds

15. Business

17. Cloud

19. Control Service
Cost

21. You must be here
Control Service
Cost

22. The role of IT
Address business needs with technology (SERVICE)
 Identify technological solutions
 Address suitability, cost, and risk
Deliver an optimized solution (COST)
 On-premise platforms and infrastructure
 Existing services
 Commercial off-the-shelf (COTS) software
 Customized solutions (traditional “development”)
Manage service portfolio (CONTROL)
 Interoperability
 Service management (performance, capacity, redundancy, cost)
 Information management (security, compliance, information lifecycle)

23. Control Service
CENTER OF EXCELLENCE
Cost

25. Microsoft Cultural Shift
Cross-company cooperation
 Windows, Servers & Tools, Office, Azure
 Unified experiences
Connected services
Cross-platform, cross-device
 Windows (8, RT, 7), Windows Phone (7-8), Xbox
 HTML5
 iOS (iPad, iPhone), Android
Developers! Developers! Developers!
 Modern, cloud-ready app models
 “Only” 20% of the world‟s developers are .NET developers
 “Bring your own platform”

28. End User (Business) Value

29. Share

30. Built for

31. Cloud Services On Premise
Always up-to-date 2013 versions
Rapid release cycle

33. Apps

34. What is a SharePoint App?
An extension of SharePoint capabilities
 “Self-contained pieces of functionality that extend the capabilities of a SharePoint
website” – MSDN (bit.ly/MFDnI9)
with a UI surfaced in SharePoint
 App can appear full screen (immersive) or through an IFrame
 Declarative changes to SharePoint UI to support the application
with code running elsewhere
 No custom server-side code running on SharePoint
 Can contain some declarative SharePoint artifacts
that uses CSOM or REST (OData) to interact with SharePoint
 Remote event receivers
installed by users through the SharePoint Store or App Catalog

35. App Models

36. App Models
Model Office 365 Permissions On-Prem Permissions
SharePoint Hosted
Sandbox YES YES
Full Trust NO YES
Cloud-Hosted
Provider Hosted YES OAuth via ACS YES High-Trust (S2S)
• Developer hosts
app
• Could be in Azure
Auto-Hosted YES OAuth via ACS NO
• App can deploy
website and SQL
Azure db
• Hosted in Office
365 Azure Cloud

37. Compare customization models
Full trust WSP Sandboxed WSP Apps
Where does server-side code run? Farm (w3wp.exe) Farm (User Code Service) Anywhere but farm
Scalable Based on farm Limited Highly
Who installs and removes Farm admin Site collection admin Users
Supported in SP2013 Yes Yes Yes
SharePoint Online compatible No Yes Yes
Auto-hosting compatible No No Yes
Requires local farm for developers Yes Yes No
Remote deployment and
No No Yes
debugging from Visual Studio

39. Challenges with WSP solutions
Full-trust solutions
 Performance and stability concerns
 Incompatible with SharePoint Online
Sandboxed solutions
 Clunky architecture, too limiting
Requires administrative deployment and support
Lifecycle management
 Upgrade, decommission
Steep learning curve
Not cloud ready
 Scalability
 Multi-tenant aware

40. Benefits of the new app model
• Familiar app concepts & components
• Find apps in SharePoint Store or app catalog
• Self-service provision, upgrade and delete
Info Workers
• Leverage existing knowledge & expertise
• Manage application lifecycle independently of platform
• Revenue potential of SharePoint Store
Developers
• Govern the visibility and availability of applications
• Manage service independently of applications
• Customizations pose virtually no risk to service
IT Managers

41. Mindset
Apps for SharePoint are like apps for phones
 User driven
 Independent of the underlying platform
 Often, consuming or exposing external services and content

42. Business OS of the Cloud

44. Change of Approach
Out-of-box
 SharePoint (browser)
 SharePoint Designer
 InfoPath
 SharePoint clients (Office)
Third-party, commercial off-the-shelf (COTS)
Extensions of functionality & capabilities
 Apps
 Consume SharePoint services: Search, BCS, Metadata, Profiles…

45. Change of Architecture
User Interface
 JavaScript
 HTML
 Native applications
Business Logic
 Any language, anywhere
 .NET running in Azure, PHP, …
Data
 SQL Azure, MySQL, …
Interaction with SharePoint
 REST
 CSOM (JavaScript, .NET)

46. Change of Skillset
Server-side full-trust C# (or VB.NET)
Now more JavaScript and REST API aligned

47. CSOM

48. CSOM
Same object models as before
 .NET Managed code
 JavaScript
 Silverlight
Much richer API compared to 2010

49. OData

50. OData
REST-ful API
Virtually same coverage as CSOM

51. Change of Skillset
Server-side full-trust C# (or VB.NET)
Now more JavaScript and REST API aligned
Learn now
 TechDays
 Pluralsight: JavaScript for C# Developers
http://www.pluralsight.com/training/Courses/TableOfContents/js4cs
 Microsoft SharePoint 2013 App Development (MS Press, Scot Hillier)
http://www.amazon.com/Microsoft%C2%AE-SharePoint%C2%AE-2013-App-
Development/dp/0735674981
Get started
 Sign-up
 Download/Install Tools

52. Future Ahead

53. The Brave New Hybrid World
Infrastructure platforms
Versions
Workflow engines
Customization approaches
App hosting models
Interactions with SharePoint
Development language
Development tools

54. MAHALO! (thank you!)
http://tiny.cc/danholmepresentations
http://bit.ly/danholmearticles
http://bit.ly/danholmebooks
A HUI HO! („til next time!)
dan.holme@intelliem.com
@danholme