Upgrading SLFE from 2007 to 2010

1. Philadelphia SharePoint CommunitySharePoint (2010 & 2007)

2. Administrators

3. Developers

4. Architect Council after every meeting

5. Free Training before every meeting

6. www.TriStateSharePoint.com [coming in December]

7. Hosted blogs for members

8. Community Forums

9. Exclusive content / pre-release content

10. Meeting recordings

11. Free training

12. www.officegeeks.org/philly [until December]CONTACT: tss@mannsoftware.comTWITTER: @tristateSPScheduled Speakers

13. Todd Bleeker

14. Rob Bogue

15. Eric Shupps

16. John Holliday

17. Ben Curry

18. Asif Rehmani

19. Paul Schaeflein

20. Brett Lonsdale

21. Nick Swan

22. (and more)

23. Topics

24. Upgrade to 2010

25. SharePoint 2010 Development

26. No-Code Workflows

27. Client object model

28. Records Management

29. Business Connectivity Services

30. Sandbox Solutions

31. SharePoint Tools in Visual Studio 2010

32. Social Media

33. List Enhancements

34. Workflows

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

36. ContentBuilding a new solutionUpgrading an existing solutionVersion management

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

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

39. 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*

40. Building a New Solution Before you begin…SharePoint web parts are still supported for backwards compatibility

41. Do not change base for existing web parts!!!Creating a new web part?Inherit from ASP.NET!

42. Building a New SolutionBefore you begin…

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

44. 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…)

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

47. Building a New SolutionCreating a new solutionOpen VS2010

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

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

51. IntroducingVisual Web Part

52. Building a New SolutionChoose template: visual web partThis project template cannot be sandboxed

53. Building a New SolutionChoose template: visual web partProject created with all web part files for you

54. Building a New SolutionChoose template: visual web partA feature will be created for you automatically

55. Building a New SolutionChoose template: visual web partA package will be created for you automatically

56. Building a New SolutionChoose template: event receiverThis project template can be sandboxed

57. Building a New SolutionChoose template: event receiver“Create project” WizardNew types of receiversNew events to handle!

58. Building a New SolutionChoose template: event receiverAdds all needed files for you

59. IntroducingBusiness Data Catalogue Tools

60. Building a New SolutionChoose template: BCS modelThis project template can be sandboxed

61. Building a New SolutionChoose template: BCS modelBCS editing tools

62. Building a New SolutionChoose template: BCS modelPackaged and deployed as a farm level feature

63. Building a New SolutionChoose template: content typeThis project template can be sandboxed

64. Building a New SolutionChoose template: content type“Create content type” WizardMore work needed on the wizard though… 

65. Building a New SolutionChoose template: list definitionThis project template cannot be sandboxed

66. Building a New SolutionChoose template: list definition“Create List Def.” Wizard

67. Building a New SolutionChoose template: content typeSchema FileCreate Elements file for featureOptional: Create list instance XML

68. Building a New SolutionChoose template: content typePackaged and deployed as a web feature

69. Building a New SolutionChoose template: workflowThis project template cannot be sandboxed

70. Building a New SolutionChoose 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

71. Building a New SolutionChoose template: workflow“State machine” wizardChoose history and tasks lists.* Also choose a list if you selected a list workflow typeWorkflow initiation options

72. Building a New SolutionChoose template: workflowDesigner has different options for site and list workflows

73. Building a New SolutionChoose template: workflowAdd sequential workflow, with its own designer

74. Building a New SolutionChoose template: workflowCreates separate elements file for each workflow

76. IntroducingYour very own sandbox!

77. Building a New SolutionSetup trust levelChoose your destiny

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

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

80. 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…

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

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

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

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

86. 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!

87. Building a New SolutionAdding new componentsAdd mapped folder

88. Building a New SolutionAdding new componentsAdd other components

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

91. 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 package (customizable!)Retract = removes the solutionpackage from server

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

93. Upgrading an Existing SolutionUpgrading an existing solution

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

95. Upgrading an Existing SolutionUpgrading non-VSeWSS solutionCase 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

96. Upgrading an Existing SolutionUpgrading non-VSeWSS solutionSLFE version 1.*.*

97. Upgrading an Existing SolutionUpgrading non-VSeWSS solutionWhat we added in 2010:List settings ribbon buttonsAdd CSS file using DelegateWSP packaging

98. Live DemoSLFE ProjectLive demo of SLFE in Visual Studio 2010

99. Upgrading an Existing SolutionUpgrading non-VSeWSS solution2010 New UIRibbon (resizable)Using image store filesand CSS class

100. Live DemoSLFE SolutionLive demo of SLFE in SharePoint

101. Upgrading an Existing SolutionUpgrading non-VSeWSS solutionConclusionIn 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!

102. Upgrading an Existing SolutionUpgrading non-VSeWSS solutionSteps for upgrading a projectEstimated ~1 hour to 4 hours of 1 developer to have the solution ready for packaging.

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

104. Upgrading an Existing SolutionUpgrading 2005/2008 VSeWSSUnfortunately, 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.”

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

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

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

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

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

110. Live DemoSLFE SolutionImporting WSP package

111. Upgrading an Existing SolutionImporting a WSP package

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

113. 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!

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

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

119. Version ManagementUp/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

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

121. ContentBuilding a new solutionUpgrading an existing solutionVersion management

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

123. Contact UsFor more information on SharePoint 2010 please don’t hesitate to contact us!At our booth out side

124. Email: shai@kwizcom.com

125. Online: http://www.kwizcom.com

126. Blog: http://kwizcom.blogspot.com* Learn * Plan * Deploy * Build *Call to learn how KWizCom can assist you!

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

128. KWizComContact:Shai Petel (shai@kwizcom.com)VP R&D, Microsoft Certified TrainerKWizCom Corporation

Upgrading SLFE from 2007 to 2010

More Related Content

What's hot (10)

Similar to Upgrading SLFE from 2007 to 2010 (20)

Recently uploaded (20)

Upgrading SLFE from 2007 to 2010

Editor's Notes