1. Server Development Overview Paul Appleby & David Gristwood Application Architects Developer & Platform Group Microsoft Limited

2. Session Goals This session is all about “what”, not “how” Cover the pieces of Windows SharePoint Services version 3 and Microsoft Office SharePoint Server 2007 fit together Enumerate the places within SharePoint Products and Technologies where you can add your own code Guide you to the right sessions to cover the specific development projects you have in mind Provide a big picture – but a technical big picture

3. Agenda SharePoint architecture Development areas Microsoft Office SharePoint Service Shared services model

4. Session Roadmap

5. SharePoint’s Dual Nature Two different but valid views of 1.A storage application Lists, Views, Libraries, Versioning, Security, etc 2.A Web application interface Pages, Web Parts, Security, etc

11. Fundamental Principle #1 Site definition basic unit of work Defines every single site …are made up of features New to version 3 Are “capabilities” e.g. tracking, basic collaboration, etc …which reference components e.g. web parts, event handlers, etc …that may talk to shared services e.g. Search

12. Fundamental Principle #2 SharePoint sites: Consist of data And only data, no “code behind” Unlike ASPX programs in Visual Studio Can reference code events, Web Parts, pages, workflow assemblies SharePoint is a runtime engine that brings together all the elements on demand to create a page Based on who you, what you asked for, etc

13. Fundamental Principle #3 Shared Services is the new model for manageable, enterprise scalable sites Microsoft Office SharePoint Server provide and use these Windows SharePoint Services doesn’t ship with any shared services OOB Shared Services must: Expect to be used by multiple Web applications from multiple farms Make themselves able to be surfaced in and managed via SharePoint Central Administration** Allow themselves to be managed by delegated administrators

14. Operating System Services Database Search Workflow ASP.NET () ASP.NET ( Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc. ) Core Workspace Services StorageRepositoryMetadataVersioningBackupSecurityRights/Roles Pluggable Auth Per Item Rights Trimming Management Admin UX DelegationProvisioningMonitoringTopology Config. Mgmt. Farm Services Feature Policy Extranet Site Model RenderingTemplatesNavigation Visual Blueprint APIsFields/Forms OM and SOAP EventsDeployment Collaboration Discussions Calendars E-Mail Presence Project Mgt. “Lite” Offline Enterprise Content Mgmt. Authoring Approval Web Publishing Policy/Auditing Rights Mgt Retention Multi-Lingual Staging Personalization My Sites Targeting People Finding Social Networking Privacy Profiles Search Indexing Relevance Metadata Alerts Customizable User Exper. Business Process Integration Rich Forms Web Forms Biz Data Catalog Data in Lists LOB Actions Single Sign-On BizTalk Integr. Business Intelligence Server Calc. Web Rendering KPIs Dashboards Report Ctr. SQL RS Int. SQL AS Int. Project Tasks Schedules Resources Budgets Deliverables Reports Applications/Portals SharePoint Technology Stack

15. Development Areas Main areas you can hook in to: 1. Data 2. Metadata 3. Behavior 4. ASP.NET extensions 5. Packaging

16. 1 - Data SP has lots of data Documents Calendars / Contacts / Announcements / Links / Surveys / Discussions … Lists, libraries, views Programmatic access to data and documents Update list, change status Access via SP object model

17. 2 - Metadata Extensive used Field definitions, list definitions, site definitions New focus on Content Types Reusable definition of a list schema Specific fields Hierarchical Associate Behaviors Events, Document Templates, Workflows E.g. different types of business documents Marketing, reports, expenses, change request

18. 3 – Behavior (Events) Events allow developers to modify the way SharePoint behaves when working with data call a web service, update a back end system, etc Events supported on lists and libraries Before and after events Pre-synchronous with cancellation and filtering Enforce business logic Can register multiple event receivers Attach Events at Web or Item Level

19. Session Roadmap

20. Behavior (Workflow) SharePoint hosts Windows Workflow Foundation Attach workflow to data in SP Can start manually or automatically Workflows OOB Workflow Workflow related activities Workflow user interactions Tools Visual Studio SharePoint Designer

21. Session Roadmap

22. 4 - ASP.NET Extensions It’s no longer “should I use ASP.NET or SharePoint sites?” It’s “should I use ASP.NET to write from scratch or to extend SharePoint sites?” SharePoint has great strengths around provisioning and re-use Web Parts Custom controls Custom pages User/role providers

23. Session Roadmap

24. 5 - Packaging Developers supporting admins Ease deployment and roleout Features Address storage and manipulation Encompasses list / view/Web Part / Event Handler / workflow component / etc. Part of a Site Definition Sharable across site definitions

25. Agenda SharePoint architecture Development areas Microsoft Office SharePoint Service Shared services model

26. Microsoft Office SharePoint Server Many major pieces of server functionality in Office 2007 involve adding a feature and a shared services to WSS Microsoft Office SharePoint Server is the ultimate SharePoint development example Most of Microsoft Office SharePoint Server 2007 consists of: Features (with lots of components) Site Definitions Blogs, wikis, meeting workspaces, document workspaces, Shared Services e.g., Indexing, Search, Excel, InfoPath Forms

27. Operating System Services Database Search Workflow ASP.NET () ASP.NET ( Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc. ) Core Workspace Services StorageRepositoryMetadataVersioningBackupSecurityRights/Roles Pluggable Auth Per Item Rights Trimming Management Admin UX DelegationProvisioningMonitoringTopology Config. Mgmt. Farm Services Feature Policy Extranet Site Model RenderingTemplatesNavigation Visual Blueprint APIsFields/Forms OM and SOAP EventsDeployment Collaboration Discussions Calendars E-Mail Presence Project Mgt. “Lite” Offline Enterprise Content Mgmt. Authoring Approval Web Publishing Policy/Auditing Rights Mgt Retention Multi-Lingual Staging Personalization My Sites Targeting People Finding Social Networking Privacy Profiles Search Indexing Relevance Metadata Alerts Customizable User Exper. Business Process Integration Rich Forms Web Forms Biz Data Catalog Data in Lists LOB Actions Single Sign-On BizTalk Integr. Business Intelligence Server Calc. Web Rendering KPIs Dashboards Report Ctr. SQL RS Int. SQL AS Int. Project Tasks Schedules Resources Budgets Deliverables Reports Applications/Portals WSS vs. MOSS Development More code-intensive development More component, feature development More declarative development More solution development, integration work Room to extend with components, client UI

28. Excel Services Architecture Excel engine available on the server Central storage - “one version of the truth” Protect business logic Web Part allows users to view / interact with live workbook using browser Web Services allows programmatic access Use as calculation engine No VBA or macros supported Use User-Defined Functions (UDFs)

32. Session Roadmap

33. InfoPath Form Services WSS Provides back end processing for InfoPath “InfoPath for the web” Server side generation / handling of forms Users do not require InfoPath client Forms developed with InfoPath editor Template parts (“formlets”) Visual Studio Tools for Applications (VSTA) (VSTO is Office specific VSTA) Forms become content type on publish Content type is responsible for extra UI Enables re-use

35. Session Roadmap

36. Business Data Catalog Integration of back end system data into SharePoint No custom code needed Define metadata that describes business entities Used for Display, indexing, etc BDC aware Web Parts Add columns to lists, etc Custom actions Look up, write-back, etc Metadata management tools

37. Business Data List Web Part Business Data column in a list Action inside a Business Data List Web Part

38. Session Roadmap

39. SharePoint Collaboration Technology Higher-value application level resources Tracking items, project tasks, issue tracking e.g. Issue tracking supports sending email when ownership assigned Wiki, Blog, discussions, etc Email integration Lists can now receive emails Can write custom email handlers Directory services integration Create/manage distribution lists

42. Session Roadmap

43. Search Services Customize/extend Search Center Set of Custom Search Web Parts Add tabs with custom actions Modifying the Search Core Results Web Part XSLT Customize alerts Search engine exposed through API Index custom data Protocol handlers and IFilters Business Data Catalog

44. Search Services SharePoint search limited to within current site collection Office Search can search file shares, Exchange, external web sites, etc

48. Session Roadmap

49. Fundamental Principles SharePoint site definitions are made up of features which reference components that may talk to shared services SharePoint sites consist of data described by definitions that can reference code and contain instancing information for components Shared Services are high-value, resource- intensive processes that can be managed within SharePoint Central Administration by delegated administrators

50. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.