SharePoint Developer Education Day Palo Alto

  • 10,010 views
Uploaded on

This is the deck from my day-long presentation to some NorCal .NET developer UGs

This is the deck from my day-long presentation to some NorCal .NET developer UGs

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • City Real Estate Europe - http://www.cityorbestate.com


    عقار - http://www.3qarsa.net

    حكايات نواعم - http://www.nem-stories.com/vb/
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
10,010
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
460
Comments
1
Likes
5

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • MGB 2003 © 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Transcript

  • 1. SharePoint for Developers Lynn Langit Developer Evangelist Microsoft http://blogs.msdn.com/SoCalDevGal
  • 2. About me Foundations of SQL Server 2005 Business Intelligence (APress) SharePoint Architect SharePoint Instructor MSDN Developer Evangelist
  • 3. 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
  • 4. 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
  • 5. 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
  • 6. Portals for everyone
  • 7. 2007 Office System Capabilities Fundamentals Enterprise Content Management Business Intelligence Communication and Collaboration Individual Impact
  • 8. 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
  • 9. 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 .
  • 10. Portal Development Areas Portal Sites People and Expertise Search My Site Targeting and Personalization Profile Store Improvements
  • 11. Search Customization Enterprise search Top results on first page Revamped ranking engine
  • 12. What is SharePoint?
  • 13. 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
  • 14. SharePoint as a developer platform
  • 15.
    • 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
  • 16.
    • 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
  • 17. SharePoint Designer HTML Controls
    • standard HTML controls
    • Form Controls
  • 18. SharePoint Designer ASP.NET 2.0 Controls
    • Standard
    • Data
    • Validation
    • Navigation
    • Login
    • Web Parts
  • 19. SharePoint Designer SharePoint Controls
    • Data View Controls
    • Server Controls based on current site
    • Page Fields (publishing)
    • Content Fields (publishing)
  • 20. SharePoint Designer Editing a SharePoint site
    • Open site
    • Enter credentials
    • Work with pages & content!
  • 21. Working with SharePoint Designer
  • 22. 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
  • 23. 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
  • 24. Working inside Visual Studio
  • 25. 15 minute break
  • 26. What Will We Cover?
  • 27. What are the fantastic 40?
  • 28. 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
  • 29. 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
  • 30. Sites, Site Collections, Templates
  • 31. What is a Content Type?
    • Information about content
    • Metadata (columns)
    • Strongly typed
      • inheritable
    • Defined using XML
      • Site admin tools or programmatically
    • Available globally
  • 32. 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
  • 33. Profile Properties
    • A special kind of content type
    • Extendable
    • Mapped to Active Directory (LDAP) – default provider
  • 34. Working with Content Types
  • 35. 1-hr lunch break
  • 36. What Will We Cover?
  • 37. 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
  • 38. 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
  • 39. Libraries – specialty web parts
    • Libraries vs. Lists
    • Library characteristics
      • Metadata
      • Views
    • Documents
    • Pictures
    • Forms
  • 40. 3 types of libraries in SharePoint
  • 41. Libraries - advanced
    • Base document type(s)
    • Custom metadata
      • Content Types
      • Re-package library as content type (feature)
    • Permissions
      • Menu options
    • Workflow
  • 42. Customizing libraries inside of SharePoint
  • 43. 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)
  • 44. 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
  • 45. Web Parts in action
  • 46. 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
  • 47. Using Visual Studio for Web Part Development
    • Use ASP.NET template
    • Use Toolbox section for Web Parts
      • WebPartManager or SharePointWebPartManager
      • WebPartZone
      • More
  • 48. How to create Web Parts in Visual Studio
  • 49. 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
  • 50. 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
  • 51. 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
  • 52. Deploying Web Parts as Features
  • 53. 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
  • 54. Using & Customize InfoPath forms
  • 55. 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
  • 56. Create a Form – using various methods
  • 57. Form deployment
    • File (shared folder)
    • Web site
    • SharePoint library
    • Other
  • 58. Form deployment
  • 59. Forms Services in SharePoint
    • Configuring the SSP
      • Shared Services Provider
    • Security considerations
    • Deploying the form
    • Using the form via SharePoint libraries
  • 60. Deploying to forms services
  • 61. Advanced capabilities
    • Tablet (ink) support
    • Digital signatures
    • Attachments
    • SharePoint workflows
  • 62. 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
  • 63. Why use Workflows?
    • Reusable – multiple sites, pages, libraries
    • Inheritable – from base workflows
    • Visually documented
    • Capture business logic
    • Customizable by authorized users
      • Public properties
  • 64. 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
  • 65. Workflows in action
  • 66. 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
  • 67. 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
  • 68. 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)
  • 69. Using SharePoint Designer for Workflow Development
    • Customize existing SharePoint workflows
    • Create new workflows
      • Use Workflow Designer Wizard
    • Creates XOML file
  • 70. Creating Workflows in SharePoint Designer
  • 71. 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
  • 72. 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
  • 73. 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
  • 74. 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
  • 75. How to create Workflows in Visual Studio
  • 76. 15 minute break
  • 77. What Will We Cover?
  • 78. 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
  • 79. 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
  • 80. What does it look like?
  • 81. Using BDC content from AdventureWorks 2000
  • 82. 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
  • 83. 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
  • 84. 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
  • 85. Create an ADF for the BDC
  • 86. 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
  • 87. Configure the ADF for the BDC
  • 88. 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…)
  • 89. Working with BDC data in MOSS
  • 90. 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
  • 91. Lynn Langit Developer Evangelist Microsoft Corporation http://blogs.msdn.com/SoCalDevGal