1. Windows SharePoint Services v3.0 Martin Parry Developer & Platform Group Microsoft Limited martin.parry@microsoft.com www.martinparry.com

2. A Quick Plug... 10 th May 2008 http://www.developerdayscotland.com

3. Agenda From ASP.NET to SharePoint SharePoint terminology primer SharePoint Schema Developing & deploying your features SharePoint extensibility points WebParts

4. Windows SharePoint Services Anyone with a Windows Server license can download and install WSS Anyone licensed to access a Windows Server can access WSS Installs with an embedded SQL Server No extra SQL license required for this, but... To scale up, you need separate SQL Server Which needs to be licensed separately

5. From ASP.NET to WSS v3.0 Developer creates provisioning infrastructure per site Multiple sites = duplicating infrastructure One provisioning infrastructure for thousands of sites

6. ASP.NET vs. WSS ASP.NET Content typically filesystem-based Must be copied across a server farm Few customisation opportunities for the user Each site designed & implemented afresh WSS Content either in filesystem or content DB(s) DB content visible across entire farm Lots of end-user authoring and customisation Site inheritance and templating

7. Windows SharePoint Services " V2" Windows SharePoint Services “Version 2” Windows SharePoint Services “Version 3” ASP.NET 1.1 ASP.NET Integration ASP.NET 2.0 Windows SharePoint Services “V3”

8. WSS Databases WSS data and content stored in SQL Server Provides foundation for scaling to Web farm environment Configuration data stored in WSS configuration database Site content and customizations stored in content databases

9. Preparing IIS to host WSS sites Create an IIS Web Application (a.k.a. Virtual Server) Either directly via the IIS console, Or via SharePoint 3.0 Central Administration Extend the IIS Web Application Adds the configuration in the configuration database Creates folder structure Creates web configuration files No more ISAPI filter !

10. Take a look at SharePoint

11. Important WSS v3 Concepts Farm The highest-level scope for a WSS deployment An installation of one of more Web servers and back-end servers Each WSS farm has one and only one configuration DB Web Application (a.k.a. Virtual Server) An IIS Web site extended with WSS Entry point capable of hosting 10,000s of site collections Site Collection (a.k.a. Site) Unit of scale and ownership containing top-level site Stored in one specific content DB Site (a.k.a. Web) Many per site collection Uses same content DB as parent site

12. Sites and Site Collections WSS manages sites in terms of site collections Each Web Application can host one or more site collections Each site collection has exactly one top-level site A site collection may (or may not) have child sites

13. Lists and Document Libraries Containers for Storing Content Content Database List Document Library Picture Library... CAML Schemas SharePoint UI Custom Applications Smart Clients

14. SharePoint Lists List types designed to store content in form of items Each list type defines schema including set of columns List type includes Form pages (e.g. AllItems.aspx) List type can have multiple views Creating a list instance from a list type Create list instance using WSS built-in list types (e.g. Contacts) Create list instance from custom list and define columns Users can add/remove/modify columns on list instance List template used to create list type from instance List instance can be template-ized from list settings page List templates create new list types scope at site collection

15. Document Libraries WSS Document Library is a hybrid list type Provides support for uploading/storing documents Provides support for document check-in/check-out Provides support for document versioning Document images store in SQL Server content DB Document Library has a document template Document template used when user clicks New command Document Library can contain custom columns Provide easy way to add metadata to documents

16. Site Columns WSS v3 supports shared column definitions Single column definition can be reused across many lists Site column definitions stored in Site Column Gallery Site column scoped and reusable across entire site collection

17. Using Site Columns in a List Site Columns can be used in List Definition Column is defined and named once at the Site level Column can be used in multiple lists or content types Column definition can be updated in one place

18. Introduction to Content Types Foundation for content management in WSS v3 Reusable definition for list schema Defines constraints and requirements for an item type Created by users and developers Reused and extended by users Examples Proposals for software projects –Requires author –Requires data for scheduling and budgeting –Requires reviews by technical and finance departments Customer presentation –Requires author –Requires reviews by legal and art departments

19. Content Types can include… Columns to represent metadata or properties A document template on which to base documents of this type Custom forms for New, Edit, and Display use with content type Event handlers Workflows available for items of this content type Information Management policies

20. Using Content Types Site Content Types created on the site Can be re-used in multiple lists Visible in this site and all child sites Types of changes to a Site Content Type Add/remove fields or update to document template Change in policy You can decide to push down changes Changes are optionally applied to existing lists or other types which inherit from it Granular – Individual changes can be pushed down Why optionally push down changes? Allow consumers of the type to make their own customizations Admin can “Seal” a content type to prevent consumers from making changes

21. Inheriting Content Types Allows base definition reuse across multiple types Core properties can be defined in base content type Base content type inherited by more specific content types Base Document Litware Document Litware Presentation Litware Customer Report Litware Proposal

22. WSS Schema

23. What are Features? Innovation to enhance modular provisioning Group logical elements into scenario-driven “features” Features can be added to and reused across site definitions New features can be activated in existing site to add functionality Features scoped at web, site, web application, farm

24. Core Feature Components Feature Name ID Description Scope Receiver assembly Activation Dependencies Element Manifests Feature Name ID Description Scope Receiver assembly Activation Dependencies Element Manifests Feature.xml Custom Actions Custom Views Content Type Definitions Layouts Pages Modules (files) List Instances List Templates Event Receivers Delegate Controls Workflow Bindings Elements.xml

25. Feature Scopes Item Custom Actions Site Settings Links Admin Custom Actions Farm Elements Item Custom Actions Site Settings Links Admin Custom Actions Web Application Elements Site Settings Links Web Part Definitions Workflow Definitions Site Content Types Layout Files List Instances Site Collection Elements List Definition List Forms List Views List Instances List Item Events Item Custom Actions Web Admin Custom Actions Layout Files Web Elements

26. Site Collection Features Site Collection Features Farm Features Farm Features Web Features Web Features Contacts Hidden Features Visible Features Document Libraries Document Libraries Picture Libraries Picture Libraries Events Basic List Links Announce- ments Announce- ments Tasks Survey Discussion Board Discussion Board WSS Core Links WSS Core Links Core Content Types Core Content Types Content Light Up Core Column Templates Core Column Templates WSS Out-Of-The-Box Features

27. Activation Dependencies Features can be designed with dependencies Allows one feature to assume another feature is present Example: Feature B might depend on Feature A B should be written with activation dependency on A Activating B forces A to be activated as well Deactivating B results in deactivation of A Features can be defined as hidden Hides the feature from users in administration activation pages Hidden features still activated by others with dependencies

28. Making Features Available Features must be copied to \12\Template\Features folder of every Front- end Web Server Features must be installed Administrators can activate or deactivate features using The browser Using STSADM Event handlers can be hooked-up with the activate and deactivate events Stsadm.exe –o installfeature –filename myfeature\feature.xml Stsadm.exe –o activatefeature –filename myfeature\feature.xml –url url

29. WSS Solutions CAB file with.wsp extension Manifest.xml describes content Can contain... Features Template files Resource files Assemblies Must be deployed before use

30. Solution and Feature Lifecycle Add Solution Deploy Solution Activate Features Delete Solution Retract Solution Deactivate Features

31. Feature Provisioning Events <Feature Id="9D2F3359-7664-430b-9391-143A7CCD2942" ReceiverAssembly="LitwareAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xyz" ReceiverClass="Litware.LitwareFeatureReceiver" xmlns="http://schemas.microsoft.com/sharepoint/"> namespace Litware { public class MyFeatureReceiver : Microsoft.SharePoint.SPFeatureReceiver { public override void FeatureInstalled(SPFeatureReceiverProperties properties) { // event hander run after feature is installed } public override void FeatureActivated(SPFeatureReceiverProperties properties) { // event hander run after feature is activated SPWeb web = (SPWeb)properties.Feature.Parent; web.Title = "Hello World"; web.Update(); } public override void FeatureDeactivating(SPFeatureReceiverProperties properties) { // event hander run before feature is deactivated } public override void FeatureUninstalling(SPFeatureReceiverProperties properties) { // event hander run before feature is uninstalled } Define the receiver class by inheriting from SPFeatureReceiver Point to receiver class in Feature.xml (assembly must be in GAC)

32. WSS Features and Solutions

33. Other WSS Extensibility Site templates List templates Field types UI controls, replacement forms Custom actions Event receivers Server-side Object Model

34. Web Parts in WSS 3.0 WSS V2 Runtime WSS Web Parts WSS V3 Runtime ASP.NET 2.0 Runtime ASP.NET Web Parts WSS Web Parts

35. ASP.NET 2.0 Web Parts in WSS v3 Web Parts derive from WebPart base class All Web Parts inherit common functionally using System; using System.Web.UI; using System.Web.UI.WebControls.WebParts; namespace LitwareWebParts { public class HelloWorldWebPart : WebPart { protected override void OnPreRender(EventArgs e) { this.Title = "Litware Project Revenue"; } protected override void RenderContents(HtmlTextWriter writer) { writer.Write("Hello, world"); }

36. The Web Part Gallery Scoped to the Site Collection level List of Web Parts available to place on pages Web Parts declared as SafeControls can be auto- populated Web Parts imported into gallery using.webpart files

37. Connectable Web Parts Provider and consumer Web Parts Data passed is defined by custom interface Connections is part of SharePoint infrastructure Web Part Page Master Detail Data

38. Web Parts

39. Summary Provisioning framework for multiple sites Config and content* go in SQL database Flexible schema Highly customisable and extensible Developers use Features and Solutions Users can create sites and content We didn’t talk about Workflow

40. MSDN in the UK Visit http://msdn.co.ukhttp://msdn.co.uk Newsletter Events Screencasts Blogs

41. © 2007 Microsoft Ltd. 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.