Microsoft Office SharePoint 2007 Technical Enablement Tour Patrick Tisseghem (Managing Partner – U2U)

Customizing Sites and Building SharePoint Solutions

© 2006 Microsoft Corporation. The WSS Template Architecture ●WSS is a site provisioning engine ●Sites are based on templates (plenty of OOB templates) ●Template architecture of WSS is extensible 12/06/20153 Save as Template in the database (.stp file) Save as Template in the database (.stp file) Collection of physical files known as site definitions

© 2006 Microsoft Corporation. Site Definitions and the Global Template ●Reside in SiteTemplates folder on every front-end Web server ●Collection of XML files (following the CAML language) and ASPX pages acting as helper files ●Common schema definitions and helper files are factored out in the Global folder ●Site definitions are localized through resource files stored in the Resource folder 12/06/20154

DEMO Exploring Site Definitions

© 2006 Microsoft Corporation.6 The Features Framework ●Bring modularity to site definitions ●Provide greater flexibility, control and reusability ●Better story for making new functionality (e.g. new lists, menu enhancements, custom workflows,...) available on existing sites

© 2006 Microsoft Corporation. What is a Feature? 12/06/20157 Feature.xml defines the metadata of the feature Other XML files called manifest files define what the feature is all about: - Event handlers - List and library definitions - Custom workflows - Light-up of SharePoint UI - Administrative operations CAML and ASP.NET helper files representing the feature components

© 2006 Microsoft Corporation. Scope of Features ●Farm ●Web Application ●Site Collection ●Site 12/06/20158

© 2006 Microsoft Corporation. OOB WSS Features ●Team Collaboration Feature ●Announcements List Feature ●Content Types Feature ●Field Types Feature ●Administrative Links Feature 12/06/20159

© 2006 Microsoft Corporation. Making a Feature Available ●Deploy Feature –Copy the all of the files making up the feature to the Features folder ●Install Feature ●Activate Feature –Using the browser (features admin page) –Using STSADM Stsadm.exe –o installfeature -force Stsadm.exe –o activatefeature –url site

DEMO Exploring and Creating Features

© 2006 Microsoft Corporation. Web Content Management System What do we expect from it? ●An environment giving the capability to quickly build, deploy, and maintain highly dynamic Web sites: –Branding: Rich and flexible support for defining the look, feel, and navigation of the site –Decentralized Authoring: Allow users to create and contribute content with a few simple clicks using tools they already know! and using templates that developers have created. Get Information Technology out of the publication business! –Workflow/Scheduling: Allow supervisors to approve content before it is posted. –Data Integrity: Enforce the ‘freshness’ of data. Ensure your documents go up and come down off the site at the right time. Ensure mandates are met. –Policy, Procedures, and Guidelines: Gentle and transparent enforcement of agencies content policies, procedures, and guidelines via templates

© 2006 Microsoft Corporation. Web Content Management Business Managers Site Designers and Web Developers Content Creation and Approval, Publishing, Scheduling, Archiving, Versioning Site Managers Business Users / Content Creators Site Structure, Templates, Site Design, Integration, Business rules, Security Mobile Devices Web Sites Web Services Workflow

© 2006 Microsoft Corporation. Microsoft Content Management Server 2002 ●Low TCO/Enterprise CM - Separate content from design –Dynamically repurpose and target content for audiences and devices –Deliver fast and low-cost site updates and redesigns –Provide content versioning, scheduling and reuse ●Enhance Biz User Productivity – Empowered to Publish –Web browser-based rich authoring or direct from Microsoft Word –Out-of-the-box and extensible workflow for compliance and quality control ●Powerful Abilities for IT – Extensible and Interoperable –Developers rapidly create content-rich, dynamic Web applications –VS.NET integrated providing out-of-the-box server and user controls –Templates easily created by dragging and dropping placeholders –Managed API leveraging.NET framework and ASP.NET –Web Services extensibility –Integration with SharePoint Portal Server and Commerce Server ASP.NET

© 2006 Microsoft Corporation. Design Goals ●Integrate CMS and SharePoint –Remove forced choice “CMS vs. SharePoint” –Move towards integrated ECM solution –Add Internet readiness to Sharepoint ●Make creation of dynamic, produced websites dramatically faster and easier –Lower amount of costly custom code –Provide great OOB experience –Improve user experience across all features ●Move CMS customers forward –Comprehensive data migration –Enable flexible migration plans

© 2006 Microsoft Corporation. CMS vNext ●Part of the Microsoft Office SharePoint Server 2007 ●Delivered as a set of features ●Option for internet/extranet/intranet ●Towards an integrated ECM solution ●Excellent OOB experience 12/06/201516

© 2006 Microsoft Corporation. Investments ●Forms Authentication ●Master Pages ●Page Model ●Smart Client Authoring ●Publishing Cycle ●Site Variations ●WCM Web Parts 12/06/201517

Demo Web Content Management with MOSS 2007

© 2006 Microsoft Corporation. CMS 2002 to MOSS 2007 ●Two phases of migration –Content migration (automatic) –Application migration (manual) ●Content migration support two modes –Full migration –Incremental migration ●Start with a full migration and then do periodic incremental migrations until you are ready to cut over –Incremental allows you to continue using your existing CMS02 installation during migration ●CMS 2002 and MOSS 2007 can coexist on the same physical farm –This allows you complete the migration without having to purchase hardware for a new farm

© 2006 Microsoft Corporation. CMS 2002 Content Migration ●Content migration tool runs against CMS02 –Generates import packages ●What counts as content? –Channels, postings and all placeholder content –Resource galleries and resources –Template galleries and template gallery items (not the ASPX files) –Rights groups and users –Custom properties ●What will I have after I run the automatic content migration tool? –A functioning site with all existing content –A set of unbranded page layouts that can be re-branded

© 2006 Microsoft Corporation. CMS 2002 Application Migration ●Update “white” master page and page layouts generated by the content migration tool –Reapply all custom formatting logic e.g. adding custom CSS classes –Should only need to touch one master page and a handful of page layouts

© 2006 Microsoft Corporation. CMS 2002 Application Migration Custom code

© 2006 Microsoft Corporation. WSS v2 vs. WSS v3 Event Handlers ●An event handler is a.NET assembly containing one or more classes handling events that are triggered by SharePoint ●WSS v2 –only possible for document libraries –executed in an asynchronous manner ●WSS v3 events architecture significantly improved –Events supported for lists, document libraries and content types –Events supported for changes to list schema as well as items –Events supported at site collection and site level –Events supported for incoming messages –Support for synchronous events and asynchronous events –Synchronous events occur before the fact and are cancel-able

© 2006 Microsoft Corporation. Steps for Creating an Event Handler ●.NET class library –Reference to Microsoft.SharePoint.dll –Custom class inheriting a WSS receiver class using Microsoft.SharePoint; namespace Demos { public class MyEventHandler: SPItemEventReceiver { public override void ItemDeleting(SPItemEventProperties properties) { // do something and possibly cancel the event properties.Cancel = true; properties.ErrorMessage = “my message"; } public override void ItemDeleted(SPItemEventProperties properties) { // do something }

DEMO Building a WSS v3 Event Handler

© 2006 Microsoft Corporation. Deploying a WSS v3 Event Handler ●Compile class into strong-named assembly ●Deploy the DLL in GAC ●Register DLL as event handler in WSS v3 –The WSS v2 way (only for document libraries) –Programmatically via the object model –Using the new WSS feature framework

DEMO Deploying and Registering a WSS v3 Event Handler

© 2006 Microsoft Corporation. Web Part History ●Windows SharePoint Services 2.0 (WSS) –Designed with its own Web Part infrastructure –WSS serializes/stores/retrieves personalization data ●ASP.NET 2.0 –Designed with newer universal Web Part infrastructure –Serializes/stores/retrieves personalization data –More flexible and more extensible than WSS –ASP.NET 2.0 does not support WSS v2 Web Parts ●Windows SharePoint Services 3.0 (WSS) –Backward-compatible with v2 Web Parts –Offers a layer on top of the ASP.NET 2.0 Web Part infrastructure

© 2006 Microsoft Corporation. Web Part Types for WSS v3 WSS v2 Runtime WSS Web Parts WSS v3 Runtime ASP.NET 2.0 Runtime ASP Web Parts Hybrid Web Parts WSS Web Parts

© 2006 Microsoft Corporation. WSS v3 Web Part Page Structure SPWebPartManager SPWebPartZone (Left)SPWebPartZone (Right)Editor Zone Catalog Zone Web Part 1 Web Part 2 Web Part 3 Web Part 4 Web Part 5 Editor Part 1 Editor Part 2 Catalog Part 1 Catalog Part 2

© 2006 Microsoft Corporation. Developing a WSS 3.0 Web Part ●Web Parts derive from ASP.NET 2.0 WebPart base class using System; using System.Web.UI; using System.Web.UI.WebControls.WebParts; namespace MyWebParts { public class HelloWorldWebPart : WebPart { protected override void OnPreRender(EventArgs e) { this.Title = “Hello Web Part"; } protected override void RenderContents(HtmlTextWriter writer) { writer.Write("Hello, world"); }

DEMO Developing a WSS 3v3 Web Part

© 2006 Microsoft Corporation. Deployment Steps ●Deploy the.NET assembly –As private assembly in the \bin folder –As shared assembly in the Global Assembly Cache (GAC) ●Register the Web Part as a safe control ●Add the Web Part to the Web Part gallery available at the site collection level ●Advertise the Web Part in the ‘Add Web Part’ dialog

DEMO Deploying a WSS v3 Web Part

Questions?

Section title here Sub title here