Presentation is loading. Please wait.

Presentation is loading. Please wait.

Paul Andrew Technical Product Manager Microsoft Session Code: OFC204.

Similar presentations

Presentation on theme: "Paul Andrew Technical Product Manager Microsoft Session Code: OFC204."— Presentation transcript:


2 Paul Andrew Technical Product Manager Microsoft Session Code: OFC204

3 Agenda Types of applications to build and tools to use Demo – build a web part using a data list Application lifecycle management integration Overview of best practices More demos

4 Types of Applications to Build Collaborative business applications Line of Business applications Small intranet applications One page apps – web part, data list, In the Portal Customize enterprise SharePoint workloads Portal Collaboration Business Process Business Intelligence Search Content Management SharePoint public web content management

5 Solution Development Roles Creates content for Content Managed Site Modifies SharePoint lists and views Adds web parts to pages Information Worker Does site design of HTML and CSS Builds simple workflows Creates and publishes InfoPath Forms Create Data View web parts Designer or Power User Writes new web parts and web services Builds custom code for WSP deployment Builds complex workflows in code Professional Development Coder

6 Professional Development Coder Custom Coding Custom web parts Site definitions List definitions Content types Microsoft Visual Studio 2008 Designer or Power User or Developer Create lists and doclibs Design Web pages No-code data view/forms Web part hookup SharePoint Designer 2007 + Browser Collaborative Development

7 Visual Studio SharePoint Tools Roadmap SharePoint 2007 and SharePoint 2010 F5 Deploy Debug WSP Packaging SPSolGen WSP View Visual Studio 2005 VSeWSS 1.0/1.1 SharePoint Sequential Workflow SharePoint State Machine Workflow Visual Studio 2008 64 bit support WSP View Improved Separate Package Command Command Line Build Visual Studio 2008 VSeWSS 1.2/1.3 Multiple Visual Designers Packaging and Deployment TFS integration Extensible Projects and Tools Visual Studio 2010 Upgrade Tool Mar 2007 / Feb 2008 Nov 2007 June 2008 / Mar 2009 2010

8 1. Separate Deployment Commands VSeWSS 1.3 New Features

9 2. Command Line Builds VSeWSS 1.3 New Features

10 3. Support for Productive Dev Builds VSeWSS 1.3 New Features

11 4. Auto Web Part Renaming VSeWSS 1.3 New Features

12 5. Deployment Conflict Resolution VSeWSS 1.3 New Features

13 6. Better WSP View Cleanup VSeWSS 1.3 New Features

14 7. 64 Bit Support VSeWSS 1.3 New Features

15 8. Deploy Additional Assemblies VSeWSS 1.3 New Features

16 VSeWSS 1.3 What You Get Item templates Web part Event receiver List definition Content type Field control Module Root file Template List instance List definition from content type

17 VSeWSS 1.3 What You Get WSP View, Package, Solution Generator, etc. WSP View (CTRL W-I) Rearrange features Add feature receivers Package and retract SETUP.BAT Solution generator User guide and help Project templates Workflow in VS2008

18 VSeWSS 1.3 Getting Started Dev Site Web parts Data lists Event handlers Workflow Silverlight web parts Page navigation Page branding Web services Content types User management Online hands on labs Downloadable VPC image Training videos

19 VSeWSS 1.3 Getting Help Use the MSDN SharePoint Forums Call Support if it is critical http://support. http://support.

20 Visual Studio 2010 SharePoint Tools Packaging Explorer Web Page Editing Create, explore, and debug SharePoint projects Web part, page and workflow designers Package and deploy SharePoint projects Team foundation server integration Support for SharePoint sandboxed solutions Broad SharePoint Support Import WSP from SharePoint designer including workflow Package and deploy Office Business Applications (OBA) Extensibility for development of additional SharePoint artifacts SharePoint Business Connectivity Services support

21 Build a Web Part Using a Data List

22 Application Lifecycle Management What is it? The coordination of all aspects of software engineering— including the following: The formulation and communication of business and technical requirements Code design and architecture Project tracking Change management Coding, testing, debugging Release management—by using tools that facilitate and track collaboration among and within work teams

23 Artifacts Requiring ALM in SharePoint Code C# or VB.NET, May include design artifacts Developers Built in Visual Studio Checked into Team Foundation Server Content Text and Images Users Built in the SharePoint HTML UI Checked into SharePoint site Design HTML, CSS, Theme, List Schema, Page Structure Designers Built in SharePoint Designer Checked into SharePoint site

24 Artifacts Requiring ALM in SharePoint Content Versioning Create a Pages Document Library Turn on versioning Covert master page to versioned /2008/11/07/page-versioning-v2.aspx Environment Deployment Content Deployment

25 Artifacts Requiring ALM in SharePoint Design Versioning Can approach same as content if using SharePoint Designer Can export to Visual Studio environment Environment Deployment Direct - Content Deployment Via Visual Studio - WSP

26 Artifacts Requiring ALM in SharePoint Code Versioning Team Foundation Server integration Add project to source control & add \pkg folder \pkg holds feature names and manifest details Delete - feature names gone Require read write from Visual Studio In TFS Explorer mark \pkg for Shared Checkout Environment Deployment WSP Solution Automated Builds Manual WSP Build Project Original: XML, GUIDs, Batch Files, STSADM Patterns and Practices SharePoint Guidance Solution with VSeWSS 1.2 VSeWSS 1.3 Added Support for Direct DEVENV.EXE Build Visual Studio 2010 Supports MSBuild stand alone builds

27 SharePoint Guidance from P&P Code

28 Automated Builds

29 Artifacts Requiring ALM in SharePoint Content Design Code How do you manage lifecycle across all three? Users create site content Developers create software Designers work on content and site structure What is the issue? SharePoint Designer acts on site instance Visual Studio creates site templates as WSP What to do about the mismatches? 1. Keep them separate 2. Merge them together

30 Artifacts Requiring ALM in SharePoint Content Design Code – Environment Setup Developers Workstations Visual Studio 2008 extensions for SharePoint Local SharePoint Install Designers Workstations SharePoint Designer & Local SharePoint Install Run STSADMExtractFiles Build Automation Server Merge artifacts in Visual Studio project Developers work on Code Designers work on Master Pages Page Layout Styles Images Site Columns Content Types List Templates Extract SPD Files to Visual Studio WSP Project STSADMExtractFiles GenSiteColumnsXML SPSolGen

31 Artifacts Requiring ALM in SharePoint Content Design Code – Environment Setup

32 ALM for Workflows Versioning and Deployment Specifics Choose the workflow starting point Built in workflows SharePoint Designer workflows Visual Studio workflows Migrating workflows from SharePoint Designer to Visual Studio Third -party guidance Looks promising e.g. Emile Bosch oolkit oolkit e.g. Todd Bleeker SharePoint Workflow Projects Separate Solutions as Visual Studio 2008 has in box support Deploy SharePoint Workflow using WSP asham/archive/2009/01/22 /how-to-deploy-a- workflow-with-vsewss-1- 3.aspx

33 Development Best Practices Patterns and practices Artifact version upgrade Test driven development Team development and continuous integration Three patterns Developer best practices resource center for SharePoint Best practices: common coding issues Do not use SPList.Items White paper: working with large lists Memory management and SPDisposeCheck Article and tool

34 Development Best Practices SPDisposeCheck 1.3.1 and Dispose Guidance SharePoint API’s return IDisposable objects Managed memory and unmanaged memory Dispose for unmanaged memory Primarily SPSite and SPWeb objects ULS Logs show leaks Simple Advice Using statements Best practice article for disposable objects us/library/aa973248.aspx SPDisposeCheck tool Evaluates Assemblies Do not run on Prod Server Run in Automated Build Can Ignore Specific Errors /SPDisposeCheck

35 SPDisposeCheck

36 Ten New Themes for VSeWSS 1.3 VSeWSS projects Compile and deploy to SharePoint Use in your projects Link on my blog










46 XX

47 SharePoint Server 2010 Development What’s public about SharePoint Server 2010 now? The new product name SharePoint Server 2010 Ref: The new developer tools Visual Studio 2010 SharePoint tools Ref: Ref: visual-studio.aspx visual-studio.aspx Ref: Studio-2010/ Studio-2010/ Ref: F07A783026F6/VisualStudio2010_ProductOverview.pdf F07A783026F6/VisualStudio2010_ProductOverview.pdf SharePoint Designer is now free Ref: Tools roadmap VSeWSS 1.3 now and Visual Studio 2010 in the future An upgrade tool and written guidance for customers moving from SharePoint 2007 to SharePoint Server 2010

48 Summary Types of applications Visual Studio 2008 and VSeWSS 1.3 Visual Studio 2010 SharePoint Tools Getting Started - Getting Help - SharePoint ALM - Content Design Code Patterns and practices SharePoint guidance SPDisposeCheck and dispose guidance Some cool themes

49 Resources Paul Andrew’s Blog MS SharePoint Developer VSeWSS 1.3 March CTP Release D505199C49F6 D505199C49F6 MSDN Forums for SharePoint Patterns and Practices SharePoint Guidance Application Lifecycle Management Resource Center for SharePoint Developer Best Practices Resource Center for SharePoint Reflector Typemock Isolator for SharePoint SPDisposeCheck


51 Microsoft Confidential

52 VSeWSS 1.3 What's New Features Added or Improved Develop on x64 Build commands package, deploy and retract Command line build, package and retract continuous integration and build servers Refactoring support for renaming of Web Parts WSP View improvements Deleting feature elements Merging features Adding event receivers to features Defining features as Web, Site, WebApplication, Farm Solution Generator works with publishing sites Deployment to BIN (instead of GAC) using Partial Trust RootFiles project item template F5 optionally removes conflicting existing features WSP Packaging can now include ancillary assemblies Workflow projects Site Definition items shown in WSP View New fast debugging for advanced users Improvements in messages logged for troubleshooting User Guide is now installed with the extensions

53 Team Development Basic One Developer Environment setup Windows Server 2003 or 2008 x86 or x64 VPC or Local Install WSS (search: SharePoint.EXE SP1) or MOSS Eval (search: MOSS SP1 Eval) SQL is not required But SQL Server Developer can be useful If you are still on Visual Studio 2005 Visual Studio extensions for WF VSeWSS v1.1 Workflow templates are in the WSS SDK VPC for VS2008 development with WSS 3.0 SP1 (1.8Gb Download)

54 Patterns and Practices Guidance P&P Test Driven Development Makes use of Typemock Isolator Creates Mock Objects Doesn’t require SharePoint site instance nit-testing-Microsoft- SharePoint.html Also guidance that doesn’t require Typemock Update on g g P&P Artifact Versioning Site columns Content types Web parts Files and modules Application pages User controls List item event handlers Workflows

55 Sessions On-Demand & Community Resources for IT Professionals Resources for Developers Microsoft Certification and Training Resources Microsoft Certification & Training Resources Resources

56 Track Resources Spin the Wheel: Attend SharePoint breakout sessions Mon-Thurs and collect the picture of the day. Come by the booth for a chance to spin the SharePoint wheel. Collect all 4 pictures and enter to win a Microsoft Arc Mouse, drawing 11:30am on Friday, game cards at the booth. Product Info Product Info Dev Resources SharePoint MSDN Web Site: SharePoint Developer Resources: Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. SharePoint Conference 2009 ITPro Resources SharePoint Tech Center: SharePoint Tech Center: SharePoint Best Practices: SharePoint Best Practices: us/office/sharepointserver/bb736746.aspx us/office/sharepointserver/bb736746.aspx

57 Attend an Interactive Theater Session and enter to win a Microsoft ARC Mouse Attend any SharePoint Breakout Session day 1 – 4 and check the last slide for a daily picture. Come to the TLC yellow area, SharePoint booths OFC 4 & 5 to spin the wheel for a chance to win a prize. The wheel only spins when the SharePoint spotlight is flashing. One spin per person. Collect all four daily SharePoint pictures and enter to win a Microsoft ARC Mouse. Game cards can be picked up at the booth. Drawing for Mice on Friday at the wheel at 11:30AM. Monday’s Picture is: Red Carpet Collect the SharePoint Session Picture of the Day

58 Complete an evaluation on CommNet and enter to win! Required Slide


60 © 2009 Microsoft Corporation. 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. Required Slide

Download ppt "Paul Andrew Technical Product Manager Microsoft Session Code: OFC204."

Similar presentations

Ads by Google