SharePoint is an awesome development platform, but it was hard for developers to quickly understand SharePoint development because it required knowledge of SharePoint architecture and infrastructure. Changes have been made in SharePoint 2010 but more importantly Visual Studio 2010 to improve the development experience familiar for ASP.NET developers like easy deployment and debugging of your SharePoint applications and designers for building different types of SharePoint customizations.

1. SharePoint Server 2010 a ASP.NET Developer Platform Ivan Sanders SharePoint MVP, Architect DeveloperDimension Solutions inc. ivan@dimension-si.com

3. Agenda SharePoint Basics Packaging and Deployment Common Artifacts Remote Applications Demo InfoPath Form List Definitions Event Receivers Work Flow

4. SharePoint Basics

5. Why SharePoint? SharePoint .NET 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 Server Farm 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 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. Packaging and Deployment DEMO

15. Common Tools Common Artifacts DEMO

16. SharePoint 2010 Development Development on Windows 7 or Vista x64 Visual Studio 2010 Support SharePoint Explorer SharePoint Project and Item Templates Visual Designers for Common Scenarios F5 Debugging Packaging Support (.wsp) Developer Dashboard Sandbox Solutions Client Object Model Silverlight .NET ECMA Script

17. Windows 7 Development Desktop DEMO

18. 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

19. Building an InfoPath Form DEMO

20. 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

21. 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 Creating a List Definition and Attaching an Event Receiver Content Database Code Item Added

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

23. .NET framework version SharePoint 2010 has a dependency on .NET 3.5 Workflows in SharePoint Server 2010 are *not* WF 4.0 Workflows .NET Framework release schedule doesn’t align with SharePoint Server 2010 Would have delayed SharePoint Server 2010 significantly to take a dependency on WF 4.0

24. 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

25. SPD Workflow Import NEW! SPD has a new reusable declarative Workflow template Once deployed it can be saved to a template (.wsp) Template can be imported into Visual Studio 2010 and modified Deploy Package Save to File System Create New ProjectImport WSP File system WSP

26. SPD Workflow Export and Visual Studio 2010 DEMO

27. Q & A

28. Who can you trust?? The blogs I trust through all of the noise. Maurice Prather http://www.bluedoglimited.com/default.aspx Andrew Connell http://www.andrewconnell.com/blog Spence Harbarhttp://www.harbar.net Jim Duncan Heather Solomon http://www.heathersolomon.com/blog Todd Klindthttp://www.toddklindt.com/default.aspx Todd Baginskihttp://www.toddbaginski.com/blog Todd Bleekerhttp://bit.ly/edlSm5Jan Tielenshttp://weblogs.asp.net/jan Patrick Tisseghemhttp://www.u2u.info/Blogs/Patrick/default.aspx WictorWilenhttp://www.wictorwilen.se Ted Patissonhttp://blog.tedpattison.net/default.aspx Lars Fastruphttp://www.fastrup.net CarstenKeutmannhttp://keutmann.blogspot.com Keith Richie http://blog.krichie.com Bill Baer http://blogs.technet.com/b/wbaer