1. Collaboration and Storage with WSS v3
6/22/2018 4:17 PM
Collaboration and Storage with WSS v3
Patrick Tisseghem
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. Agenda Architectural Changes Storage Enhancements Building Web Parts
The WSS v3 Features Framework

3. WSS v3 as a Solutions Platform
WSS v3 supplies core workspace services
Particularly suited for building scalable Web-enabled applications
WSS v3 provides out-of-box collaboration solutions
WSS v3 provides platform for Office Server Solutions
Office Server Solutions Built On WSS v3
Collaboration
ECM
Portal
Search
BPM BI
Project
WSS v3 Core Workspace Services
Storage
Repository
Metadata
Versioning
Backup
Security
Rights/Roles
Pluggable Auth
Per Item
Rights Trimming
Mgmt
Admin UX
Delegation
Provisioning
Monitoring
Topology
Config Mgmt
Farm Services
Feature Policy
Extranet
Site Model
Rendering
Templates
Navigation
Visual Blueprint
APIs
Fields/Forms
OM and SOAP
Events
Deployment
Operating System Services
ASP.NET 2.0 (Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc.)
Database
Search
Workflow

4. ASP.NET 2.0 Benefits
WSS integration in line with best practice ASP.NET extensibility
Virtual path provider enables for ASP.NET pages from database
Enhanced Web Part infrastructure
Master Pages feature for page templates
Rich navigation infrastructure

5. Master Pages Master Pages are a primary feature in ASP.NET 2.0
Provides effective template solution for pages within site
Content page reuses chrome from master page
Content page fill in placeholders defined in master page
WSS v3 embraces ASP.NET master pages
WSS sites such as Team Site built using a standard master page
Quick and easy to change look and feel of entire site
Editing master page can be done with SharePoint Site Designer

6. WSS Master Page Implementation
6/22/2018
WSS Master Page Implementation
How do master pages work in WSS?
Each site page in WSS site “points” to a master page
Each WSS site has a Master Page Gallery (MPG)
Site metadata tracks site-wide master page
Content pages (e.g., default.aspx) default to the per-site MPG
Form pages (e.g., allitems.aspx) default to the per-site MPG
Application pages hard-coded to master page in /_layouts 6

7. Creating and Customizing a WSS Team Site
6/22/2018 4:17 PM
Creating and Customizing a WSS Team Site
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8. General Storage Enhancements
Modified and new column types
Multi-value lookup field, append-only fields, ...
Column indexing
Versioning
List items as well as documents can be versioned
Document can have minor and major versions
Minor (e.g. 1.1)  draft version
Major (e.g. 2.0)  published version
Version status can be used for hiding/displaying document, in approval, scheduling and other workflow scenarios
Version pruning now supported
Version history page shows metadata changes

9. General Platform Enhancements
6/22/2018 4:17 PM
General Platform Enhancements
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

10. Site Columns Central, reusable model for column definitions
Scoped at the site collection level in the Site Column Gallery
Once created, use it in any list or library
Changes to the site column can be pushed to the lists and libraries making use of it

11. 6/22/2018 4:17 PM
Site Columns
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

12. Content Types
A reusable collection of settings you want to apply to a certain category of content
Metadata
Behaviors
Created at site collection level
Inheritance
Document
Report
Sales Report
Marketing Report
Legal Report

13. Using Content Types
Switch list/library to enable multiple content types
Add one or more content types
New button
Shows different content types
Administrator can change order and hide/display content types
Changes done at the content type level are immediately affecting lists/libraries by default
Reports Doc Lib
Sales Reports
Marketing Reports
Legal Reports

14. 6/22/2018 4:17 PM
Content Types
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

15. Integration with Outlook 2007
Take lists and libraries offline
Only ‘Outlook-type’ of lists (contacts, tasks, events)
Any document libary
WSS content is stored in its own pst file
2-way synchronization via ‘Send and Receive’
Central management dialog in Outlook

16. Integration with Outlook 2007
6/22/2018 4:17 PM
Integration with Outlook 2007
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

17. Web Part History Windows SharePoint Services 2.0 (WSS) ASP.NET 2.0
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

18. Web Part Types for WSS v3
WSS v3 supports 3 different types of Web Parts
ASP.NET 2.0 Runtime
WSS v3 Runtime
WSS Web Parts
ASP Web Parts
ASP Web Parts
Hybrid Web Parts
WSS v2 Runtime
WSS Web Parts
WSS Web Parts

19. WSS v3 Web Part Page Structure
Web Part Page in WSS is designed with…
One instance of SPWebPartManager class
One or more SPWebPartZones
Editor Zones and Catalog Zones supplied by WSS pages
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

20. ASP.NET 2.0 Web Parts Web Parts derive from WebPart base class
All Web Part 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");

21. Building v 3 Web Parts

22. The Web Part Gallery Scoped to the Site Collection level
Contains list of Web Parts available to place on pages
Web Parts declared as SafeControls can be auto-populated
Click New button on toolbar
Web Parts imported into gallery using .webpart files
Click Upload button on toolbar

23. Building and Deploying v3 Web Parts
6/22/2018 4:17 PM
Building and Deploying v3 Web Parts
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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

25. Synchronous vs Asynchronous Events
Synchronous events end at –ing
E.g. ItemDeleting
WSS waits before code returns TRUE before performing action in database
Asynchronous events end at –ed
E.g. ItemDeleted
Executed in new worker thread
Action in WSS
Before event fired by WSS
Event handler executes code
Event handler
Executes code
WSS commits action
WSS does not commits action
After event fired
Event handler executes code

26. Scope of Events

27. Creating an Event Handler - Steps
.NET class library
Reference to Microsoft.SharePoint.dll
Custom class inheriting a WSS receiver class
SPItemEventReceiver or SPWebEventReciever
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

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

29. Programmatically Registering the Event Handler
Console or Windows application
private void RegisterForList (string site, string web, string listname, string assembly, string class) {
SPSite site = new SPSite(site);
SPWeb web = site.OpenWeb(web);
SPList list = web.Lists[listname];
list.EventReceivers.Add (SPEventReceiverType.ItemDeleting, assembly, class);
list.EventReceivers.Add (SPEventReceiverType.ItemDeleted, assembly, class); }

30. Creating and Deploying Event Handlers
6/22/2018 4:17 PM
Creating and Deploying Event Handlers
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

31. Site Provisioning with WSS
Two-step process
Creation of a site at a specific URL
Populating the site based on a site template
Windows SharePoint Services is designed to be a platform that can support different types of sites  the template architecture can be extended
Site templates
Use browser to save an existing site as a template
Stored in the database
Can be extracted as STP file
Create site definition
Collection of files making up the template
Stored on the front-end Web server as a physical folder

32. Packaging Solutions with WSS v3

33. What is a feature? 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

34. Out-of-the-box Features
6/22/2018 4:17 PM
Out-of-the-box Features
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

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

36. Creating, installing and activating custom features
6/22/2018 4:17 PM
Creating, installing and activating custom features
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

37. Review Architectural Changes Storage Enhancements Building Web Parts
The WSS v3 Features Framework

38. © 2006 Microsoft Corporation. All rights reserved.
6/22/2018 4:17 PM
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.