Microsoft SharePoint Server 2010 for the Microsoft ASP.NET Developer

1. SESSION CODE: OSP316 Microsoft SharePoint Server 2010 for the Microsoft ASP.NET Developer Eric Shupps President BinaryWave

2. About Me • Windows SharePoint Services MVP • President, BinaryWave • President, International SharePoint Professionals Association • Member, Patterns & Practices Advisory Board (spg.codeplex.com) • Web: www.binarywave.com • Blog: www.sharepointcowboy.com • Twitter: @eshupps • Facebook: www.facebook.com/sharepointcowboy

3. Agenda • SharePoint Basics • Packaging and Deployment • Common Artifacts • Remote Applications • Demo • Visual Web Parts • List Definitions • Event Receivers • Client Object Model

4. SharePoint Basics

5. Why SharePoint? • .NET • SharePoint Custom Development • Data Storage • Data Storage Out of the Box • Presentation • Presentation • Security • Security • Clustering • Clustering • API’s • API’s • Office Integration • Office Integration • Features • Features Custom

6. SharePoint Terminology Timer Job Web Part Layout Page Elevated Privileges CAML Farm Safe Control Content Type Site Column Declarative Workflow Feature STSADM Site Collection Application Page Persisted Object Site Definition Solution Package Scope Event Receiver Content Database List Definition Central Administration Publishing Page Theme Web Application ONET List Instance List View Feature Receiver Team Site Field Control Client Object Model

7. SharePoint Architecture Server Farm Databases Solutions Service Applications Alternate Access Monitoring Security Policies Web Application Providers File Types Service Connections Throttling Managed Paths Quotas Permissions Site Collection Templates Web Parts Features User Solutions Content Types Site Columns Content Database Web Features Lists Views Workflows Themes Layouts Alerts

8. Server Farms • A collection of SharePoint role servers and a SQL database server • Servers can perform one or more functions (web front end, search, application, etc.) • Farm-level features are managed via Central Administration • Custom code can be deployed at the Farm level and managed centrally • Solution Packages allow custom code to be automatically deployed across the farm Server Farm Web Front Ends Application Database

9. Web Applications and Site Collections • Web application = IIS Virtual Server • Each web application may be assigned its own app pool • Web applications may utilize multiple service applications • Site collections reside within web applications • Site collection functionality derived from underlying site definition • Special site collection types include My Sites, Shared Services Provider, Publishing Web Portal HR Finance Marketing MySites Central Administration

10. Packaging and Deployment

11. Solution Packages • Solution Packages are “bundles” of functionality deployed to the farm or site collection (sandbox) • May contain one or more Features, assemblies, pages, controls, and other artifacts • SharePoint framework handles installation and configuration of solution items automatically across entire farm • Automated packaging and deployment in Visual Studio 2010

12. Sandbox Solutions • Trusted solutions which run in isolated process • Load balanced execution • Uploaded to solution directory in site collection • Administratively controlled via quotas • Can be automatically disabled • Subset of OM functionality • Ability to use trusted proxy for restricted operations MyWebPart.dll Runtime Full Object Model Subset Object Model Proxy

13. Features • A ‘Feature’ is a defined set of functionality encapsulated within a specific format • Features are the basic building block of WSS v3 and MOSS development • Features may be comprised of any combination of code, including web parts, workflows, and site definitions • Features may be deployed manually or automatically on a local or global basis • Features are heavily dependent on CAML

14. Common Artifacts

15. Web Parts • Web Parts are a specific type of server control that inherit from System.Web.UI.WebPart • Web Parts contain discreet functionality that is exposed to the user in the context of a Web Part Page • Classic Web Parts do not have an IDE; Visual Web Parts host ASP.NET User Controls • Web Parts execute in the context of the current user • Web Parts may be deployed individually or in conjunction with other artifacts

16. Building a Visual Web Part DEMO

17. List Elements, Types and Views • Lists are virtual data repositories for unstructured content • Fields defined by associated content types and user-defined columns • Common lists types included OOTB • Custom list types may be created in UI or code • List data is stored in the content database associated with the site collection • Maximum limit for list items is 30M+ • Be aware of performance implications and throttling when storing/retrieving large amounts of list data • Lists have associated views defined in UI or CAML • Custom field types may be created programmatically

18. Event Receivers • Event Receivers are handler assemblies that respond to events on specific objects (Webs, Lists, Features, etc.) • Event receivers override built-in methods: • Adding/Added • Updating/Updated • Activated/Deactivated • Installing/Uninstalling • Event Receivers have no UI or user feedback mechanism • Event Receivers must run with Full Trust in the GAC Code Item Adding Content Database Code Item Added

19. Creating a List Definition and Attaching an Event Receiver DEMO

20. Relational Data • LINQ to SharePoint • CAML joins varq = fromannouncement indc.announcements whereannouncement.Expires >= DateTime.Today select new { announcement.Title, announcement.Body }; <Joins>     <Join Type='LEFT ListAlias='List1'>         <Eq>             <FieldRef Name='Field1' RefType='Id' />             <FieldRef Name='ID' List='List1' />         </Eq>      </Join>     <Join Type='LEFT' ListAlias='List2'>         <Eq>             <FieldRef List='List1' Name='SomeFieldName' RefType='Id' />             <FieldRef List='List2' Name=’ID’ />          </Eq>     </Join> </Joins>

21. Workflow • SharePoint Workflow inherits and builds upon Windows Workflow Foundation (WF) • Simple workflows can be created in SharePoint Designer, advanced workflows require Visual Studio • Two types of workflow – Sequential and State Machine • User interaction provided via InfoPath forms or custom ASPX pages • Workflows are tied directly to lists and list items • Built-in history, tasks, and tracking mechanisms

22. Remote Applications

23. Web Services • SharePoint Web Services provide remote access to a number of Object Model functions • Web services are limited in scope to several primary functional areas, such as Farm, Site, Web, List, List Items, List Views, etc. • Web services require a great deal of XML manipulation • Many web service functions require a solid understanding of CAML • Custom web services should be deployed as WCF solutions • Can increase load on Web Front End Servers • Deploy isolated WFE if used heavily

24. REST • HTTP-based XML data transfer • Stateless, cacheable, uniform • Conforms to Atom Publishing Protocol • Direct integration with SharePoint Services (Excel) and Lists • Sample queries: • http://myserver/_vti_bin/listdata.svc • http://myserver/_vti_bin/ExcelRest.aspx/Docs/Documents/sampleWorkbook.xlsx/model/Ranges('Sheet1!A1|G5')

25. Client Object Model • Subset of server OM functionality • .NET, Silverlight, JavaScript • Sync and Async processing • Request throttling • Batch object handling Browser JavaScript Controls Client Service Server Object Model JavaScript OM Proxy Proxy Managed OM Content Database Managed Controls Client Server

26. Building a Client Object Model Application DEMO

27. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Track Resources • For More Information – http://sharepoint.microsoft.com • SharePoint Developer Center – http://msdn.microsoft.com/sharepoint • SharePoint Tech Center – http://technet.microsoft.com/sharepoint • Official SharePoint Team Blog – http://blogs.msdn.com/sharepoint

28. Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Related Content • Breakout Sessions – See Conference Guide for full list of OSP Track Sessions • Interactive Sessions – OSP Track has 10 Interactive Sessions – OSP01-INT – OSP10-INT • Hands-on Labs – OSP01-HOL – OSP20-HOL • Product Demo Stations – Yellow Section, OSP • Office 2010, SharePoint 2010, Project Server 2010, Visio 2010 have kiosks and demos

29. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

30. Required Slide Complete an evaluation on CommNet and enter to win!

31. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

32. Play the Microsoft Office & SharePoint Track Tag Contest Download the Microsoft Tag Reader Open the internet browser on your mobile phone and visit http://gettag.mobi Grand Prize (1) Xbox 360 Prize Package and Microsoft® Office 2010 Daily Prizes 40 copies of Microsoft® Office 2010 Come to the Expo Hall – Yellow Section OSP Info Desk for Official Rules & Collect Additional Tags from all OSP Track Sessions, Speakers and Expo Hall!

33. © 2010 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.