SharePoint for Developers Lynn Langit Developer Evangelist Microsoft http://blogs.msdn.com/SoCalDevGal

About me Foundations of SQL Server 2005 Business Intelligence (APress) SharePoint Architect SharePoint Instructor MSDN Developer Evangelist

What Will We Cover? SharePoint Developer Platform Dev setup, tools, templates Container Objects & Metadata Templates, sites, collections, pages, content types User Objects Web parts, Lists, Libraries, Workflows, InfoPath Data & Security SSP, BDC, Excel Services

SharePoint Developer Platform

Dev setup, tools, templates

Container Objects & Metadata

Templates, sites, collections, pages, content types

User Objects

Web parts, Lists, Libraries, Workflows, InfoPath

Data & Security

SSP, BDC, Excel Services

Schedule Session 1- 9 am to 10 am Session 2 – 10:15 to 12 Lunch – 12 to 1pm Session 3 – 1 pm to 2:15 pm Session 4 – 2:30 to 4:00 pm Giveaways & Wrap Up

Session 1- 9 am to 10 am

Session 2 – 10:15 to 12

Lunch – 12 to 1pm

Session 3 – 1 pm to 2:15 pm

Session 4 – 2:30 to 4:00 pm

Giveaways & Wrap Up

Convergence SharePoint Portal Server 2001 SharePoint Team Services “v1” Content Management Server 2002 SharePoint Portal Server 2003 Windows SharePoint Services “v2” Windows SharePoint Services v3 Office SharePoint Server 2007

Portals for everyone

2007 Office System Capabilities Fundamentals Enterprise Content Management Business Intelligence Communication and Collaboration Individual Impact

SharePoint Functional Architecture Operating System Services Platform Services Applications and Services Collaboration Portal Search Content Management Business Processes Business Intelligence Shared Services Security Site Model Extensibility Deployment Management Storage ASP . NET Database Services Search Services Workflow Services

ECM in SharePoint Server 2007 ECM Components Records Management Web Content Management Forms Management Document Management User Interface Microsoft Office Web browsers 3 rd -party apps Unified Stora ge Architecture Unified Services Workflow Metadata Policies Search Security IRM Collab Library Svcs .

Portal Development Areas Portal Sites People and Expertise Search My Site Targeting and Personalization Profile Store Improvements

Search Customization Enterprise search Top results on first page Revamped ranking engine

What is SharePoint?

SharePoint Developer Environment Within SharePoint Re-use existing items Change default items Extend default items Re-use customized items Wire-ups – data, forms, workflows, more

Within SharePoint

Re-use existing items

Change default items

Extend default items

Re-use customized items

Wire-ups – data, forms, workflows, more

SharePoint as a developer platform

Windows Server 2003 or 2008 IIS 6.0 or 7.0 WSS 3.0 Database SQL WMSDE or SQL Server SharePoint Server (Usually) Virtual Server or PC (Usually) Office Professional 2007 (Usually) Visual Studio 2005 or 2008 SPS Developer Environment

Windows Server 2003 or 2008

IIS 6.0 or 7.0

WSS 3.0

Database

SQL WMSDE or SQL Server

SharePoint Server

(Usually) Virtual Server or PC

(Usually) Office Professional 2007

(Usually) Visual Studio 2005 or 2008

Part of the Office Suite ASP.NET 2.0 support Tool for Web designers for ASP.NET 2.0 Great design and development experience with Expression Web and Visual Studio 2005 Deep support for popular data technologies, such as XML, XSLT and RSS Built-in ASP.NET development server SPS Designer Developer Environment

Part of the Office Suite

ASP.NET 2.0 support

Tool for Web designers for ASP.NET 2.0

Great design and development experience with Expression Web and Visual Studio 2005

Deep support for popular data technologies, such as XML, XSLT and RSS

Built-in ASP.NET development server

SharePoint Designer HTML Controls standard HTML controls Form Controls

standard HTML controls

Form Controls

SharePoint Designer ASP.NET 2.0 Controls Standard Data Validation Navigation Login Web Parts

Standard

Data

Validation

Navigation

Login

Web Parts

SharePoint Designer SharePoint Controls Data View Controls Server Controls based on current site Page Fields (publishing) Content Fields (publishing)

Data View Controls

Server Controls based on current site

Page Fields (publishing)

Content Fields (publishing)

SharePoint Designer Editing a SharePoint site Open site Enter credentials Work with pages & content!

Open site

Enter credentials

Work with pages & content!

Working with SharePoint Designer

VS and SPS Downloads .NET framework 3.0 VSTO (version 2) Visual Studio 2005/8 Designer for Windows Workflow Foundation Windows SharePoint Services 3.0 Tools: Visual Studio 2005/8 Extensions WSS SDK Enterprise Content Management (ECM) Starter Kit (template for SharePoint workflows) Included in SharePoint SDK

Downloads

.NET framework 3.0

VSTO (version 2)

Visual Studio 2005/8 Designer for Windows Workflow Foundation

Windows SharePoint Services 3.0 Tools: Visual Studio 2005/8 Extensions

WSS SDK

Enterprise Content Management (ECM) Starter Kit (template for SharePoint workflows)

Included in SharePoint SDK

VS and SPS – other resources Downloads CodePlex Community Kit Forms-authentication toolkit LINQ to CAML MSDN Web Service documentation Fantastic 40, more… Blogs SharePoint Team Blog Lynn’s blog

Downloads

CodePlex

Community Kit

Forms-authentication toolkit

LINQ to CAML

MSDN

Web Service documentation

Fantastic 40, more…

Blogs

SharePoint Team Blog

Lynn’s blog

Working inside Visual Studio

15 minute break

What Will We Cover?

What are the fantastic 40?

SPS Sites & Templates are… Containers for UI (web pages which contain web parts) Containers for business logic (workflows) Containers for data display (internal and external) Containers for groups of sites (collections) Automatically added to navigation Automatically security trimmed

Containers for UI (web pages which contain web parts)

Containers for business logic (workflows)

Containers for data display (internal and external)

Containers for groups of sites (collections)

Automatically added to navigation

Automatically security trimmed

SPS Pages are… Containers for UI (web pages which contain web parts) Containers for business logic (workflows) Containers for data display (internal and external) ASP.NET 2.0 compatible Automatically added to navigation

Containers for UI (web pages which contain web parts)

Containers for business logic (workflows)

Containers for data display (internal and external)

ASP.NET 2.0 compatible

Automatically added to navigation

Sites, Site Collections, Templates

What is a Content Type? Information about content Metadata (columns) Strongly typed inheritable Defined using XML Site admin tools or programmatically Available globally

Information about content

Metadata (columns)

Strongly typed

inheritable

Defined using XML

Site admin tools or programmatically

Available globally

Why use Content Types? Reusable – multiple libraries Inheritable – from base types Strongly typed Securable Scoped to the site Can be based on internal or external data Supports standard taxonomy implementation

Reusable – multiple libraries

Inheritable – from base types

Strongly typed

Securable

Scoped to the site

Can be based on internal or external data

Supports standard taxonomy implementation

Profile Properties A special kind of content type Extendable Mapped to Active Directory (LDAP) – default provider

A special kind of content type

Extendable

Mapped to Active Directory (LDAP) – default provider

Working with Content Types

1-hr lunch break

What Will We Cover?

What is a Web Part? UI for SharePoint or ASP.NET 2.0 page Reusable ‘chunk’ of content Like a ‘smart ‘.ascx’ file Displays XML, formats via XSLT

UI for SharePoint or ASP.NET 2.0 page

Reusable ‘chunk’ of content

Like a ‘smart ‘.ascx’ file

Displays XML, formats via XSLT

Lists – the core web part type Rows and Columns of strongly typed data Most basic web part Can create, customize, extend, create from Excel Views not Folders – expose Metadata intelligently

Rows and Columns of strongly typed data

Most basic web part

Can create, customize, extend, create from Excel

Views not Folders – expose Metadata intelligently

Libraries – specialty web parts Libraries vs. Lists Library characteristics Metadata Views Documents Pictures Forms

Libraries vs. Lists

Library characteristics

Metadata

Views

Documents

Pictures

Forms

3 types of libraries in SharePoint

Libraries - advanced Base document type(s) Custom metadata Content Types Re-package library as content type (feature) Permissions Menu options Workflow

Base document type(s)

Custom metadata

Content Types

Re-package library as content type (feature)

Permissions

Menu options

Workflow

Customizing libraries inside of SharePoint

Why use Web Parts? Reusable – multiple sites, pages, libraries Inheritable – from base types Strongly typed Securable Security-trimmed by default Customizable by authorized users Public properties Connectable (can pass data for filtering)

Reusable – multiple sites, pages, libraries

Inheritable – from base types

Strongly typed

Securable

Security-trimmed by default

Customizable by authorized users

Public properties

Connectable (can pass data for filtering)

How end users use Web Parts? Customize on page Simple or Advanced properties Add to page from gallery Simple or Advanced view Create pages or sites from templates Templates can include web parts

Customize on page

Simple or Advanced properties

Add to page from gallery

Simple or Advanced view

Create pages or sites from templates

Templates can include web parts

Web Parts in action

How to get Web Parts? Download – free or purchase Customize existing from within SharePoint Create from with SharePoint Create using SharePoint Designer Create using Visual Studio

Download – free or purchase

Customize existing from within SharePoint

Create from with SharePoint

Create using SharePoint Designer

Create using Visual Studio

Using Visual Studio for Web Part Development Use ASP.NET template Use Toolbox section for Web Parts WebPartManager or SharePointWebPartManager WebPartZone More

Use ASP.NET template

Use Toolbox section for Web Parts

WebPartManager or SharePointWebPartManager

WebPartZone

More

How to create Web Parts in Visual Studio

Typical Deployment steps Create web part Copy to in or GAC Set Web.config trust level Add Web.config entry for SafeControls Add .webpart file (gallery browsing) Test webpart on a page

Create web part

Copy to in or GAC

Set Web.config trust level

Add Web.config entry for SafeControls

Add .webpart file (gallery browsing)

Test webpart on a page

What’s a Feature? Reusable chunk of content for SharePoint Can be scoped to site or subset of site Examples Content Type List Workflow Web part

Reusable chunk of content for SharePoint

Can be scoped to site or subset of site

Examples

Content Type

List

Workflow

Web part

How to implement features add subfolder with a Feature definition within Features setup directory includes Feature.xml defines the base properties of the Feature & lists elements bound to it Work with features Via SharePoint UI Using Stsadm.exe Using the SharePoint object model

add subfolder with a Feature definition within Features setup directory

includes Feature.xml

defines the base properties of the Feature & lists elements bound to it

Work with features

Via SharePoint UI

Using Stsadm.exe

Using the SharePoint object model

Deploying Web Parts as Features

What is InfoPath? RAD form-design application Data binding options Included controls Sophisticated security Integration w/ Active Directory and more Included with Office xxx version Based on XML – embeddable in ASP.NET Many deployment options

RAD form-design application

Data binding options

Included controls

Sophisticated security

Integration w/ Active Directory and more

Included with Office xxx version

Based on XML – embeddable in ASP.NET

Many deployment options

Using & Customize InfoPath forms

How do I create a Form? Customize a sample Based on a XSD schema Based on a relational data source Based on a web service Using Visual Studio

Customize a sample

Based on a XSD schema

Based on a relational data source

Based on a web service

Using Visual Studio

Create a Form – using various methods

Form deployment File (shared folder) Web site SharePoint library Other

File (shared folder)

Web site

SharePoint library

Other

Form deployment

Forms Services in SharePoint Configuring the SSP Shared Services Provider Security considerations Deploying the form Using the form via SharePoint libraries

Configuring the SSP

Shared Services Provider

Security considerations

Deploying the form

Using the form via SharePoint libraries

Deploying to forms services

Advanced capabilities Tablet (ink) support Digital signatures Attachments SharePoint workflows

Tablet (ink) support

Digital signatures

Attachments

SharePoint workflows

What is a Workflow? Unit of Business Logic Contains Activities Contains cancel & fault handlers Based on Windows Workflow in .NET 3.0 Visually Designed XOML – uncompiled –OR-- .NET language - compiled

Unit of Business Logic

Contains Activities

Contains cancel & fault handlers

Based on Windows Workflow in .NET 3.0

Visually Designed

XOML – uncompiled –OR--

.NET language - compiled

Why use Workflows? Reusable – multiple sites, pages, libraries Inheritable – from base workflows Visually documented Capture business logic Customizable by authorized users Public properties

Reusable – multiple sites, pages, libraries

Inheritable – from base workflows

Visually documented

Capture business logic

Customizable by authorized users

Public properties

How end users use Workflows? Automatic invocation –OR- Office, i.e. Word, etc… SharePoint document library Manual invocation Can associate multiple workflows with single document or library

Automatic invocation –OR-

Office, i.e. Word, etc…

SharePoint document library

Manual invocation

Can associate multiple workflows with single document or library

Workflows in action

How to get Workflows? Download – free or purchase Customize existing from within SharePoint Create from with SharePoint Create using SharePoint Designer Create using Visual Studio

Download – free or purchase

Customize existing from within SharePoint

Create from with SharePoint

Create using SharePoint Designer

Create using Visual Studio

Limits of SharePoint Designer for Workflow Development I Workflow is associated to one list or library only Can NOT package as a feature Sequential Workflows only Designing State Machine Workflows not supported

Workflow is associated to one list or library only

Can NOT package as a feature

Sequential Workflows only

Designing State Machine Workflows not supported

Limits of SharePoint Designer for Workflow Development II Designing custom Activities not supported Debugging not supported Does not support all form types, i.e. InfoPath, etc… Uses XOML – no code behind (beside)

Designing custom Activities not supported

Debugging not supported

Does not support all form types, i.e. InfoPath, etc…

Uses XOML – no code behind (beside)

Using SharePoint Designer for Workflow Development Customize existing SharePoint workflows Create new workflows Use Workflow Designer Wizard Creates XOML file

Customize existing SharePoint workflows

Create new workflows

Use Workflow Designer Wizard

Creates XOML file

Creating Workflows in SharePoint Designer

Using Visual Studio for Workflow Development Workflow templates Visual Studio templates Sequence or State Machine (Library or Console application) SharePoint Sequence or State Machine Library Activity Library

Workflow templates

Visual Studio templates

Sequence or State Machine (Library or Console application)

SharePoint Sequence or State Machine Library

Activity Library

State Machine vs. Sequential? Sequential == known, one-way flow, i.e. A, then B, then C, etc… Machine processes State == states, looping possible, i.e. meal is ordered, meal is cooked, meal is sent back, meal is updated Human processes

Sequential == known, one-way flow, i.e. A, then B, then C, etc…

Machine processes

State == states, looping possible, i.e. meal is ordered, meal is cooked, meal is sent back, meal is updated

Human processes

Workflows in Visual Studio I Code-behind workflows in C# or VB.NET Both sequential or state workflows Can include workflow modifications Can use custom activities Debugging available

Code-behind workflows in C# or VB.NET

Both sequential or state workflows

Can include workflow modifications

Can use custom activities

Debugging available

Workflows in Visual Studio II Workflows as templates Can be bound to multiple locations Can use any form type ASP forms, InfoPath, etc… Packaged as a feature

Workflows as templates

Can be bound to multiple locations

Can use any form type

ASP forms, InfoPath, etc…

Packaged as a feature

How to create Workflows in Visual Studio

15 minute break

What Will We Cover?

What is the BDC? Shared Service for MOSS allowing back-end data to be used in MOSS sites No code integration XML metadata file Application Definition File (ADF) MOSS designed to integrate Web parts, lists, search and more

Shared Service for MOSS allowing back-end data to be used in MOSS sites

No code integration

XML metadata file

Application Definition File (ADF)

MOSS designed to integrate

Web parts, lists, search and more

Why use the BDC? RAD – no code connections to data sources Back-end data can be integrated into MOSS sites Strongly typed Securable Scoped to the site

RAD – no code connections to data sources

Back-end data can be integrated into MOSS sites

Strongly typed

Securable

Scoped to the site

What does it look like?

Using BDC content from AdventureWorks 2000

What is an ADF? Metadata about data source Similar to, but not the same as, an XSD schema Required, formal structure Includes sophisticated security model (for example 5 methods of authentication supported and checkAccess() for security trimming) Samples on MSDN

Metadata about data source

Similar to, but not the same as, an XSD schema

Required, formal structure

Includes sophisticated security model (for example 5 methods of authentication supported and checkAccess() for security trimming)

Samples on MSDN

Create the ADF – hard way Manual XML copy BdcMetadata.XSD from < Root >Program FilesMicrosoft Office Servers12.0Bin to your working folder Then point the SchemaLocation attribute in the XML file to the schema location The use VS Intellisense

Manual XML

copy BdcMetadata.XSD from < Root >Program FilesMicrosoft Office Servers12.0Bin to your working folder

Then point the SchemaLocation attribute in the XML file to the schema location

The use VS Intellisense

Create the ADF – easy way Download a free ADF generator tool, such as Todd Baginski’s tool at http://www.sharepointblogs.com/tbaginski/archive/2006/07/16/9259.aspx Connect to your data source Generate the ADF Review the ADF for correctness

Download a free ADF generator tool, such as Todd Baginski’s tool at http://www.sharepointblogs.com/tbaginski/archive/2006/07/16/9259.aspx

Connect to your data source

Generate the ADF

Review the ADF for correctness

Create an ADF for the BDC

Configure the BDC Configure the SSP for the site Use the ADF file to set up the BDC connection Use a web part to test

Configure the SSP for the site

Use the ADF file to set up the BDC connection

Use a web part to test

Configure the ADF for the BDC

BDC in MOSS Works with web parts Works with lists & user profiles(i.e. add meta data) Works with custom search (i.e. search for meta data) Works with actions (i.e. update source data, etc…)

Works with web parts

Works with lists & user profiles(i.e. add meta data)

Works with custom search (i.e. search for meta data)

Works with actions (i.e. update source data, etc…)

Working with BDC data in MOSS

Session Summary Understand the new paradigm Use libraries not folders Taxonomies / metadata is key Exploit views Educate end users Explore SharePoint itself first, then SPD, then VS

Understand the new paradigm

Use libraries not folders

Taxonomies / metadata is key

Exploit views

Educate end users

Explore SharePoint itself first, then SPD, then VS

Lynn Langit Developer Evangelist Microsoft Corporation http://blogs.msdn.com/SoCalDevGal