Case Study: Upgrading SLFE from 2007 to 2010Shai Petel (shai@kwizcom.com)VP R&D, Microsoft Certified TrainerKWizCom Corporation

ContentBuilding a new solutionUpgrading an existing solutionVersion management

GoalsIn this session you will learn about the new VS2010 extensions for WSSYou will learn how to migrate your existing solutions into the new environment reducing the migration process time to minimum.This session will allow you to make better decisions on your current solutions for 2007 today that will make the transition to 2010 easy and simple.

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

Building a New Solution Before you begin…Is your team ready for 2010?Silverlight, Ajax, JSONVisual web parts! (or is it?)Prepare to be hosted!Limit customization to site collection levelPrefer to support sandboxed solutions*

Building a New Solution Before you begin…Creating a new web part?Inherit from ASP.NET!SharePoint web parts are still supported for backwards compatibilityDo not change base for existing web parts!!!

SharePoint web parts are still supported for backwards compatibility

Do not change base for existing web parts!!!

Building a New SolutionBefore you begin…

Building a New Solution Before you begin…Install all components on developer machine

Building a New Solution Before you begin…Install developer components on development client and use remote debugger to connect to development server (not so bad, but still…)

Building a New Solution Before you begin…Virtualize! (Recommended)

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

Building a New SolutionCreating a new solutionOpen VS2010

Building a New SolutionCreating a new solutionClick on new project. Go to:C# -> SharePoint -> 2010 templates

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

Building a New SolutionChoose a project templateThere are a lot of new project templates to choose from!But fear not – You can easily add any component to any project later

IntroducingVisual Web Part

Building a New SolutionChoose a project template – Visual web partThis project template cannot be sandboxed

Building a New SolutionChoose a project template – Visual web partProject created with all web part files for you

Building a New SolutionChoose a project template – Visual web partA feature will be created for you automatically

Building a New SolutionChoose a project template – Visual web partA package will be created for you automatically

Building a New SolutionChoose a project template – Event receiverThis project template can be sandboxed

Building a New SolutionChoose a project template – Event receiver“Create project” WizardNew types of receiversNew events to handle!

Building a New SolutionChoose a project template – Event receiverAdds all needed files for you

IntroducingBusiness Data Catalogue Tools

Building a New SolutionChoose a project template – Business Data Catalogue ModelThis project template can be sandboxed

Building a New SolutionChoose a project template – Business Data Catalogue ModelBCS editing tools

Building a New SolutionChoose a project template – Business Data Catalogue ModelPackaged and deployed as a farm level feature

Building a New SolutionChoose a project template – Content typeThis project template can be sandboxed

Building a New SolutionChoose a project template – Content type“Create content type” WizardMore work needed on the wizard though… 

Building a New SolutionChoose a project template – List definitionThis project template cannot be sandboxed

Building a New SolutionChoose a project template – Content type“Create List Def.” Wizard

Building a New SolutionChoose a project template – Content typeSchema FileCreate Elements file for featureOptional: Create list instance XML

Building a New SolutionChoose a project template – Content typePackaged and deployed as a web feature

Building a New SolutionChoose a project template – WorkflowThis project template cannot be sandboxed

Building a New SolutionChoose a project template – WorkflowSequential workflow is designed to execute a series of predefined steps to accomplish a certain taskState machine workflows are designed to work in event-driven scenarios. A state machine workflow contains two or more states, with one state being the active state at any given time

Building a New SolutionChoose a project template – WorkflowChoose history and tasks lists.* Also choose a list if you selected a list workflow typeWorkflow initiation options“State machine” wizard

Building a New SolutionChoose a project template – WorkflowDesigner has different options for site and list workflows

Building a New SolutionChoose a project template – WorkflowAdd sequential workflow, with its own designer

Building a New SolutionChoose a project template – WorkflowCreates separate elements file for each workflow

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

IntroducingYour very own sandbox!

Building a New SolutionSetup trust levelChoose your destiny

Building a New SolutionSetup trust levelTo trust, or not to trust?Sandbox solutions is a way for you to deploy a set of features and components to your SharePoint site collection that will have no effect on other site collectionsSandbox solutions have limited support for extensibility and not all SharePoint customizations are allowedSandboxed solutions can be installed and deployed by site owner from site settings

Building a New SolutionSetup trust levelWhat does this setting change?This setting does not get written to WSP package, but will allow VS to validate your content is supported within a sandboxes solutionSolution assemblies within a sandboxed solution are not installed to GAC/Bin, and not running on W3WP process. Instead they run under SPUCWorkerProcessSandboxed solutions can be deployed as a full-trusted solution as well

Building a New SolutionSetup trust levelWhat is supported within a sandbox solution?List Definitions, List Instances, Content Types/FieldsWeb Parts (non visual)Event receivers: Item, List or WebDeclarative workflows, Custom Actions (Ribbon)Onet.xml, WebTemplate feature element (instead of Webtemp.xml) allows for site collection level site definitions!More…

Building a New SolutionSetup trust levelWhat is not supported within a sandbox solution?Mapped folders (14 hive)Some API will not work in sandboxed modeVisual Web PartsApplication PagesCustom Action GroupHideCustomAction elementWeb Application/Farm-scoped featuresWorkflows with code

Building a New SolutionSetup trust levelHow do I deploy a sandbox solution?Upload to Solutions galleryActivate

Building a New SolutionSetup trust levelCannot activate solution?Go to central administration and make sure windows SharePoint user code service is started

Building a New SolutionSetup trust levelKeep in mind:Deploying a sandbox solution automatically activates features within (unless specifically specified not to in the feature)To disable support for sandbox solutions simply stop the user code serviceUpgrading sandbox solutions are done manually site collection at a time

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

Building a New SolutionAdding new componentsIt is extremely easy to add any component to any project you likeThis allows you to easily create more complex solutions that includes several types of customizations such as:Feature – for activationWeb parts – for visual UILists and list definitions for storing dataField types, event handlers, workflows and much more!

Building a New SolutionAdding new componentsAdd mapped folder

Building a New SolutionAdding new componentsAdd other components

ContentBuilding a new solutionCreating a new solutionChoose a project templateSetup trust levelAdding new componentsOne-click deploy or packageUpgrading an existing solutionVersion management

Building a New SolutionOne-click deploy or packageFeature and Package editors available

Building a New SolutionOne-click deploy or packageProject menu allows you to build, deploy to development server, and to package using a WSPBuild – compile code onlyPackage – compiles and builds the WSP packageDeploy – compile, package anddeploy the packageRetract – removes the solutionpackage from server

ContentBuilding a new solutionUpgrading an existing solutionUpgrading a non-VSeWSS solutionUpgrading a 2005/2008 VSeWSS solutionUpgrading a WSP packageVersion management

Upgrading an Existing SolutionUpgrading an existing solution

ContentBuilding a new solutionUpgrading an existing solutionUpgrading a non-VSeWSSsolutionUpgrading a 2005/2008 VSeWSS solutionUpgrading a WSP packageVersion management

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolutionCase study: Upgrading KWizCom SharePoint List Forms ExtensionsWhat we had in 2007:controltemplates ASCX files. New control templates and updating existing ones*Application settings pagesList settings linkFeature activated, MSI installerExternal references to utilities/shared resources

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolutionSLFE version 1.*.*

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolutionWhat we added in 2010:List settings ribbon buttonsAdd CSS file using DelegateWSP packaging

SLFE ProjectLive demo of SLFE in Visual Studiodemo

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolution2010 New UIRibbon (resizable)Using image store filesand CSS class

SLFE SolutionLive demo of SLFE in SharePointdemo

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolutionConclusionIn order to make the most of VS2010 and VS2010 extensions for WSS its best to build a new project skeleton and import existing code into it.If you already have a WSP package you can use it to build your project skeleton from it (reverse engineer) but your .NET code will not be included!

Upgrading an Existing SolutionUpgrading a non-VSeWSSsolutionSteps for upgrading a projectEstimated time: 1 hour to 4 hours of 1 developer to have the solution ready for packaging.

ContentBuilding a new solutionUpgrading an existing solutionUpgrading a non-VSeWSSsolutionUpgrading a 2005/2008 VSeWSSsolutionUpgrading a WSP packageVersion management

Upgrading an Existing SolutionUpgrading a 2005/2008 VSeWSSsolutionUnfortunately, you cannot convert VS2005/2008 projects using visual studio aloneTrying to do so will invoke this error:“The project type is not supported by this installation.”

Upgrading an Existing SolutionUpgrading a 2005/2008 VSeWSSsolutionBut fear not! VSeWSS2010 comes with a conversion tool from VSeWSS2008 only.For all other projects that used WSP for deployment - This next option might be what you are looking for!

ContentBuilding a new solutionUpgrading an existing solutionUpgrading a non-VSeWSSsolutionUpgrading a 2005/2008 VSeWSSsolutionUpgrading a WSP packageVersion management

Upgrading an Existing SolutionUpgrading a WSP packageIf you have a WSP packaged solution, you can import it into 2010!

Upgrading an Existing SolutionUpgrading a WSP packageImport wizardYour code doesnot getimported!

Upgrading an Existing SolutionUpgrading a WSP packageThe import process will build your skeleton for youAfter the import is done, some work is needed

SLFE SolutionImporting WSP packagedemo

ContentBuilding a new solutionUpgrading an existing solutionVersion managementHow can I mark versionsShared resourcesUpgrade / downgrade solution version

Version ManagementVersion managementWhy do we need version management?Tractability of bugs or changesPerform upgrade operations on existing installations (add a field, create hidden list etc.)Monitor Dev, Staging and production deployment running codeNot for ISV only!In house development team? Get used to working with versioned packages!

ContentBuilding a new solutionUpgrading an existing solutionVersion managementHow can I mark versionsShared resourcesUpgrade / downgrade solution version

Version ManagementHow can I mark versionsCannot change assembly version!Currently no supportfor marking package,but you can markfeatures:Mark versionnumber in yourcode:

ContentBuilding a new solutionUpgrading an existing solutionVersion managementHow can I mark versionsShared resourcesUpgrade / downgrade solution version

Version ManagementShared resourcesYou may need to add shared resources to your projectsDLL’s (utility classes, base classes)Sandbox – no problemGAC – no problemBIN deployment – version collisions may occur.Shared resources (Images/CSS files)Use sub folders with utilities version number.For example:/_layouts/KWizCom_Shared_2.0.01

ContentBuilding a new solutionUpgrading an existing solutionVersion managementHow can I mark versionsShared resourcesUpgrade / downgrade solution version

Version ManagementUpgrade / downgrade solution versionBuilt in support for upgrade operations!SharePoint will allow mark if feature requires upgradeMany upgrade operations supported, and custom upgrade handlers can be coded

Version ManagementUpgrade / downgrade solution versionUpgrading / downgrading is easy!Once you deploy several versions of same solution you will be able to upgrade instead of activate!

ContentBuilding a new solutionUpgrading an existing solutionVersion management

SummaryYou now have real-world experience in upgrading components into 2010There is a lot more to seeCome visit us at our booth to get the complete presentation and for 1 on 1 talks!Overall, It’s been a pleasure!

Contact UsFor more information on SharePoint 2010 please don’t hesitate to contact us!At our booth out sideEmail: shai@kwizcom.comOnline: http://www.kwizcom.comBlog: http://kwizcom.blogspot.com* Learn * Plan * Deploy * Build *Call to learn how KWizCom can assist you!

At our booth out side

Email: shai@kwizcom.com

Online: http://www.kwizcom.com

Blog: http://kwizcom.blogspot.com

Remember to fill out your evaluations onMySPCfor your chance to win two HD web cams and a designer mouse (3 prizes awarded daily)

Learn More about SharePoint 2010Information forIT Prosat TechNethttp://MSSharePointITPro.comInformation forDevelopersat MSDNhttp://MSSharePointDeveloper.comInformation forEveryonehttp://SharePoint.Microsoft.com

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