Upload
trina
View
56
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Windows SharePoint Services v3.0. Martin Parry Developer & Platform Group Microsoft Limited [email protected] www.martinparry.com. A Quick Plug. 10 th May 2008 http://www.developerdayscotland.com. Agenda. From ASP.NET to SharePoint SharePoint terminology primer - PowerPoint PPT Presentation
Citation preview
Windows SharePoint Services v3.0
Martin ParryDeveloper & Platform GroupMicrosoft [email protected]
A Quick Plug...
10th May 2008
http://www.developerdayscotland.com
AgendaFrom ASP.NET to SharePointSharePoint terminology primerSharePoint SchemaDeveloping & deploying your featuresSharePoint extensibility pointsWebParts
Windows SharePoint ServicesAnyone with a Windows Server license can download and install WSSAnyone licensed to access a Windows Server can access WSSInstalls 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
From ASP.NET to WSS v3.0Developer creates provisioning infrastructure per siteMultiple sites = duplicating infrastructure
One provisioninginfrastructurefor thousandsof sites
Windows SharePoint Services " V2"WindowsSharePointServices
“Version 2”
WindowsSharePointServices
“Version 3”
ASP.NET 1.1
ASP.NET Integration
ASP.NET 2.0
Windows SharePoint Services “V3”
WSS DatabasesWSS data and content stored in SQL Server
Provides foundation for scaling to Web farm environmentConfiguration data stored in WSS configuration databaseSite content and customizations stored in content databases
Preparing IIS to host WSS sitesCreate 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 ApplicationAdds the configuration in the configuration databaseCreates folder structureCreates web configuration filesNo more ISAPI filter !
Take a look at SharePoint
Important WSS v3 ConceptsFarm
The highest-level scope for a WSS deploymentAn installation of one of more Web servers and back-end serversEach WSS farm has one and only one configuration DB
Web Application (a.k.a. Virtual Server) An IIS Web site extended with WSSEntry point capable of hosting 10,000s of site collections
Site Collection (a.k.a. Site)
Unit of scale and ownership containing top-level siteStored in one specific content DB
Site (a.k.a. Web)
Many per site collectionUses same content DB as parent site
Sites and Site CollectionsWSS manages sites in terms of site collections
Each Web Application can host one or more site collectionsEach site collection has exactly one top-level siteA site collection may (or may not) have child sites
Lists and Document LibrariesContainers for Storing Content
ContentDatabase
List
DocumentLibrary
Picture Library
...
CAML Schemas
SharePointUI
CustomApplications
SmartClients
SharePoint ListsList types designed to store content in form of items
Each list type defines schema including set of columnsList type includes Form pages (e.g. AllItems.aspx)List type can have multiple views
Creating a list instance from a list typeCreate list instance using WSS built-in list types (e.g. Contacts)Create list instance from custom list and define columnsUsers can add/remove/modify columns on list instance
List template used to create list type from instanceList instance can be template-ized from list settings pageList templates create new list types scope at site collection
Document LibrariesWSS Document Library is a hybrid list type
Provides support for uploading/storing documentsProvides support for document check-in/check-out Provides support for document versioningDocument images store in SQL Server content DB
Document Library has a document templateDocument template used when user clicks New command
Document Library can contain custom columnsProvide easy way to add metadata to documents
Site ColumnsWSS v3 supports shared column definitions
Single column definition can be reused across many listsSite column definitions stored in Site Column GallerySite column scoped and reusable across entire site collection
Introduction to Content TypesFoundation for content management in WSS v3
Reusable definition for list schema Defines constraints and requirements for an item typeCreated by users and developersReused and extended by users
ExamplesProposals 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
Content Types can include…Columns to represent metadata or propertiesA document template on which to base documents of this typeCustom forms for New, Edit, and Display use with content typeEvent handlersWorkflows available for items of this content typeInformation Management policies
Inheriting Content TypesAllows base definition reuse across multiple types
Core properties can be defined in base content typeBase content type inherited by more specific content types
Base DocumentBase Document
Litware DocumentLitware Document
Litware Presentation
Litware Presentation
Litware Customer Report
Litware Customer Report
Litware ProposalLitware Proposal
WSS Schema
What are Features?Innovation to enhance modular provisioning
Group logical elements into scenario-driven “features”Features can be added to and reused across site definitionsNew features can be activated in existing site to add functionalityFeatures scoped at web, site, web application, farm
Core Feature Components
Feature NameIDDescriptionScopeReceiver assemblyActivation DependenciesElement Manifests
Feature.xml Custom ActionsCustom ViewsContent Type DefinitionsLayouts PagesModules (files)List InstancesList TemplatesEvent ReceiversDelegate ControlsWorkflow Bindings
Elements.xml
Feature Scopes
Farm Elements
• Item Custom Actions• Site Settings Links• Admin Custom Actions
Web Application Elements
• Item Custom Actions• Site Settings Links• Admin Custom Actions
Site Collection Elements
• Site Settings Links• Web Part Definitions• Workflow Definitions• Site Content Types• Layout Files• List Instances
Web Elements
• List Definition• List Forms• List Views• List Instances• List Item Events• Item Custom Actions• Web Admin Custom Actions• Layout Files
SiteCollectionFeatures
FarmFeatures
WebFeatures
Team Collaboration
Contacts
Hidden FeaturesVisible Features
DocumentLibraries
PictureLibraries
Events
Basic List Links
Announce-ments Tasks
Survey DiscussionBoard
WSSCore Links
CoreContent Types
ContentLight Up
Core ColumnTemplates
WSS Out-Of-The-Box Features
BasicWeb Parts
Making Features AvailableFeatures must be copied to \12\Template\Features folder of every Front-end Web ServerFeatures must be installed
Administrators can activate or deactivate features usingThe browserUsing 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
WSS SolutionsCAB file with .wsp extensionManifest.xml describes contentCan contain...
FeaturesTemplate filesResource filesAssemblies
Must be deployed before use
Solution and Feature Lifecycle
Add Solution
Deploy Solution
Activate Features
Delete Solution
Retract Solution
Deactivate Features
WSS Features and Solutions
Web Parts in WSS 3.0
WSS V2 Runtime
WSS Web PartsWSS Web Parts
WSS V3 RuntimeASP.NET 2.0 Runtime
ASP.NET Web Parts
ASP.NET Web Parts
WSS Web Parts
WSS Web Parts
ASP.NET 2.0 Web Parts in WSS v3
Web Parts derive from WebPart base classAll 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"); } }}
Connectable Web Parts
Provider and consumer Web PartsData passed is defined by custom interfaceConnections is part of SharePoint infrastructure
Web Part Page
Master
Detail
Data
Web Parts
SummaryProvisioning framework for multiple sitesConfig and content* go in SQL databaseFlexible schemaHighly customisable and extensibleDevelopers use Features and SolutionsUsers can create sites and contentWe didn’t talk about Workflow
MSDN in the UK
Visit http://msdn.co.uk NewsletterEventsScreencastsBlogs
© 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.