1. Microsoft SharePoint Server 2010 for the Microsoft ASP.NET Developer YaroslavPentsarskyy www.sharemuch.com @spentsarsky Technical Specialist Habanero Consulting

2. Agenda • SharePoint Basics • Web Parts • List Templates and Instances • List Event Receivers • Business Connectivity Services

3. SharePoint Basics

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

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

6. SharePoint Architecture Server Farm Databases Solutions Service Applications Monitoring Security Policies Web Application Providers Throttling Managed Paths Quotas Permissions Site Collection Web Parts Features Content Types Site Columns Templates Web Features Lists Workflows Layouts Alerts

7. Server Farms • A collection of SharePoint role servers and a SQL database server • Servers can perform one or more functions • Farm-level features are managed via Central Administration • Solution Packages allow custom code to be deployed across the farm Web Front Ends Application Database

8. 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 Portal HR Finance Marketing MySites Central Administration

9. Packaging and Deployment

10. Solution Packages • Solution Packages are sets 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 • Automated packaging and deployment in Visual Studio 2010

11. MyWebPart.dll Sandbox Solutions • Trusted solutions which run in isolated process • Uploaded to solution directory in site collection • Administratively controlled via quotas (can be automatically disabled) • Ability to use trusted proxy for restricted operations Runtime Full Object Model Subset Object Model Proxy

12. Features • A ‘Feature’ is a defined set of functionality encapsulated within a specific format • Features may be comprised of any combination of code, including web parts, workflows, and site definitions • Features may be deployed individually or as a part of the solution package

13. Common Artifacts

14. Web Parts • Web Parts are a specific type of server control that inherit from System.Web.UI.WebPart • Web Parts contain 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

15. Building a Visual Web Part

16. 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 • List data is stored in the content database associated with the site collection • Lists have associated views defined in UI or CAML

17. Creating a list definition

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 • Event Receivers have no UI or user feedback mechanism • Event Receivers must run with Full Trust in the GAC Code? Event Content Database

19. Attaching an Event Receiver to a List

20. Business Connectivity Service • Business Connectivity Service (BCS) is a service application managing access to external data stores using SharePoint API • BCS models define how the data is going to be accessed what operation are allowed on retrieved data • Users can view external data in a list External List List Item External Data Store

21. Creating BCS connection to a SQL Database

22. Next Steps • Download: 2010 IW Demo VM • Check out-of-the-box features of SharePoint 2010 • Download: Microsoft SharePoint 2010 SDK • Learn what can be extended in SharePoint 2010 and how to do it