1. Understand SharePoint editions and prerequisites. 2. Understand the features SharePoint offers as a development Platform. 3. Explore the differences between a site collection and a site. 4. Create site collections and sites 5. Create lists and libraries through the browser. 6. Use Web Part pages.

1. SharePoint 2010 as a Development Platform Ayman El-Hattab Technology Solution Professional MEA Center of Expertise SharePoint MVP ayman@aymanelhattab.com www.aymanelhattab.com

2. Session Objectives Understand SharePoint editions and prerequisites. Understand the features SharePoint offers as a development Platform. Explore the differences between a site collection and a site. Create site collections and sites Create lists and libraries through the browser. Use Web Part pages.

3. SharePoint Capabilities by Edition Sites Communities Content Search Insights Composites

4. Compare editions : http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx

5. System Requirements OS requirements for SharePoint 2010 Windows Server® 2008 SP2 or later Windows Server® 2008 R2 Must be 64 bit SQL requirements SQL Server 2005 SP2 or later SQL Server 2008 SP1 CU2 or later SP1 + KB970315 Must be 64 bit You can use Windows Vista or Windows 7 for your development environments. Video: http://is.gd/js2FC

6. SP2010 as a Dev. Platform SharePoint is a web application accessed through browser. Everything in SharePoint is based on templates (Web Sites, Data structure and storage components, processes, User Interface elements) Those templates are (XML + .NET) based. SharePoint has an engine to create instances of those templates. SharePoint has background services that run behind the scenes.

7. Customization Options

8. Components of a SharePoint Application SharePoint applications are called “Solutions”. Stand-alone solutions (ISV’s) Reusable components that can be used by other solutions. Consistent deployment model for devs and admins. (Portability, versioning, ALM, etc…) All solution should use the platform services and frameworks provided by SharePoint foundation.

9. Components of a SharePoint Application Data Structures and Storage User Interfaces Security Background Services Service APIs

10. Data Structures and Storage SharePoint provides services for data and content Modeling Manipulating Storing Underlying mechanisms Windows File System SQL Server For end-user, storage details are invisible. For developer, storage details are abstract (API’s).

11. Data Structures and Storage API’s API’s for working with data CAML (XML Based) Managed code JavaScript and Silverlight client libraries Various web services (SOAP, WCF and REST) API’s support Deploy data and content Define and manage data structures. Define and manage data stores. Retrieve and manipulate data and content

12. Data API's REST APIs Strongly-typed lists ClientOM Weakly-typed lists Client-side Data Storage SharePoint Data External Data ServerOM Server-side Weakly-typed lists LINQ Strongly-typed lists

13. User Interface Data is worthless without UI. Build SharePoint Web UI’s using: ASP.NET JavaScript Silverlight InfoPath (Enterprise) Services allow for any client Windows Forms WPF Non Windows Platforms

14. SharePoint 2010 Team Site

15. Major Shifts in SharePoint UI Server ribbon In-place editing Popup dialog AJAX refresh

16. Extensible UI Controls Client Side actions in Ribbon added through Custom Actions Context Sensitive Ribbon The Ribbon Status Bar Notification Area

17. Dialog Framework Keep the user in context Operations without unnecessary post packs Dialog Framework

18. Security Authentication Vs. Authorization. Windows Identity Foundation enables externalization of Authentication (Claims-Based) Scenarios: Live ID, Facebook or Twitter Authentication.

19. Background Services Long running services. Search Indexing Surfacing external data in SharePoint (BCS). Word Automation Services Service Application Framework OOB Services Custom Services Administrative and configuration interfaces (Web, PowerShell,…)

20. Service API’s Nothing is locked! Access data and services from other clients. Wide Variety: SOAP Services WCF Services REST API’s (HTTP GET Request to retrieve data) WebDAV More …

21. SharePoint Vocabulary Review FarmSPFarm Site Collections Site collection SPSite Root Site Site SPWeb Sub sites Web ApplicationsSPWebApplication Lists Document Library - SPDocumentLibrary List - SPList Field 1 Field 2 Field 3 Field 1 Field 2 Field 3 Item 1 Item 2 Item 3 Item 4 Item -SPListItem File 1 File 2 File 3 File 4 File – SPFile Folder - SPFolder

22. SharePoint Vocabulary Review Pages: UI components that enable sites to display information and interact with users. Web Part: Packaged personalizable unit of functionality that end-user can drop onto a page. Web Part Page: A pre-designed page that is designed to accept web parts. Wiki Page: Less rigid than a web part page and supports in place editing. Site Pages Vs. Site Assets Library.

23. SharePoint 2010 as a Development Platform Web Apps, Site Collections, Sites, Lists, Pages and Web Parts! demo

24. Visual Studio 2010Developer Tools for SharePoint Develop, Deploy and Debug Web Part, BCS and Workflow designers Package and Deploy SharePoint projects Generate WSP for Production Deployment View SharePoint site in Server Explorer Team Foundation Server Integration Web Part Designer Project Types

25. SharePoint Object Model

26. SharePoint Designer 2010The No code tool for SharePoint Free for creating and editing SharePoint artifacts New Tools Connect to external data List Schema Custom Actions Task / Approval Designer Improved Tools Workflow Designer Page Editor SharePoint Designer work can be upgraded to Visual Studio 2010 “Save site as template” in SharePoint Site Settings creates solution package which can be imported to VS 2010

27. The SharePoint Powershell Snapin Explicitly load SharePoint PowerShell snap-in from console or script Implicitly load snap-in by using link in Windows Start menu Begin using SharePoint Cmdlets

28. Recap: SP2010 as a Dev. Platform

30. © 2009 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.