SharePoint Connections Coast to Coast Migrating SharePoint 2007 Solutions to SharePoint 2010


Published on

In the wake of the SharePoint 2010 release, many companies are now looking to migrate their web sites from SharePoint 2007 to 2010. However, where do you start? What are the new features that enable you to migrate your site? How do you work with your developers and administrators to help them get started? If these are the questions you’re trying to answer, then you’ll not want to miss this session. You’ll learn about the features, tools and processes that will help you move your 2007 assets to 2010.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SharePoint Connections Coast to Coast Migrating SharePoint 2007 Solutions to SharePoint 2010

  1. 1. Migrating SharePoint 2007 Solutions to SharePoint Server 2010<br />VSIX extensions <br />Ivan Sanders<br />SharePoint MVP Developer, EvangelistDimension Solutions<br /><br />
  2. 2. Agenda<br />Upgrading VSeWSS projects<br />Common upgrade issues for custom code<br />Issues you might run into during upgrade your code<br />Managing your upgrade process<br />What to consider during upgrade planning for your customizations<br />
  3. 3. How to upgrade VSeWSS projects?<br />VSeWSS project upgrades<br />
  4. 4. Upgrade tool for VSeWSS<br />VS.NET Template that allow for importing of existing VSeWSS projects<br />VB and C#<br />VSeWSS 1.1 and up<br />Converts projects to Visual Studio 2010 format and maintains existing project layout<br />Availability <br />Released after RTM<br />
  5. 5. Overview<br />Template “Import VSeWSS Project”<br />Supports Full trust and sandbox solutions<br /><br />
  6. 6. Before & After<br />VisualStudio2010PackagingExplorer<br />VSEWSSWSPView<br />
  7. 7. VSeWSS upgrade<br />demo <br />
  8. 8. Project Refactoring<br />Console/WinForms Applications<br />Build as x64, .Net 3.5 SP1<br />Fix-up references<br />VS 2008/2005 Projects<br />Import WSP<br />Refactor<br />Add non-packaged files (source code, BDC, docs, scripts)<br />Fix-up references<br />Add additional support/related projects<br />
  9. 9. Refactoring Solutions<br />VSeWSS had 1:1 Feature:artifact<br />VS2010 is more flexible<br />Feature Designer<br />Add/Remove SharePoint Artifacts into features<br />From other projects in solution<br />Feature Rename, Add, Remove and Delete<br />Packaging Explorer<br />Add/Remove Features from WSP <br />Add/Remove custom assemblies<br />
  10. 10. Refactoring Your WSP<br />Refactored<br />(multiple artifacts / feature)<br />Original<br />(1 artifacts for 1 feature)<br />
  11. 11. CKS: Development Tools<br />Server Explorer<br />With CKS Extensions<br />Server Explorer<br />Default<br />
  12. 12. refactor solutions<br />demo <br />
  13. 13. Common issues you might run into<br />Upgrade issues<br />
  14. 14. Upgrade Issues<br />Site templates - STP Files<br />UI Changes<br />CSS<br />Custom Actions<br />Backwards Compatible UI<br />Large List Query Throttling<br />Deprecated API’s<br />Deployment Path issues<br />Project Refactoring<br />Other issues<br />
  15. 15. Upgrading site templates<br />Site template file format is not anymore STP<br />Need to be converted to solution packages<br />Create V3 site<br />Upgrade to V4<br />Fix any Issues<br />Save as Template<br /> STP Template<br /> .WSP<br />
  16. 16. Backwards Compatible UI <br />SP2007<br />SP2010<br />V4 Development<br />V4 UI<br />V3 UI<br />V3 UI Mode<br />Toolbars<br />V3 CSS<br />V3 Themes<br />No Interactive calendars<br />No In-Place Wiki edits<br />No Ribbon<br />( Configurable on a site by site basis )<br />
  17. 17. Site Collection Options<br />Site Settings<br /> > Site Collection Administration<br /> > Supported User Experiences<br />
  18. 18. Site Options<br />Site Settings<br />> Title, Description & Appearance (in V3 UI Mode)<br />
  19. 19. intranet upgrade<br />demo <br />
  20. 20. Object Model Options<br />Web Level<br />SPWeb.UIVersion (int values of 3 or 4)<br />Site Collection<br />SPSite.UIVersionConfigurationEnabled<br />“Preview Mode” if in V4 and UIVersionConfigurationEnabled==true<br />
  21. 21. Versioned Controls<br />Allows for rendering of version specific content.<br />During Render<br />At Load Time – handles child controls properly<br />
  22. 22. CSS Changes<br />What has changed in SharePoint CSS?<br />Almost everything!<br />Any customizations that depend on V3 CSS such as master pages will need to be redesigned to work correctly in V4.<br />Rendering based on XHTML <br />WCAG 2.0 AA level compliant<br />
  23. 23. Custom Actions<br />No more toolbars in V4 UI Mode<br />Toolbar actions are moved<br />Moved to Custom Commands on the ribbon.<br />It is possible to show ribbon and toolbar by modifying the list form web part properties.<br />Actions with code behind<br />(ControlAssembly, ControlClass, or ControlSrc attribute) don’t migrate to Custom Commands tab.<br />
  24. 24. Upgrading master pages<br />Remove unnecessary controls, which are replaced with ribbon<br />Publishing Console, Site actions, sign in and log-in controls<br />Add new place holders<br />PlaceHolderQuickLaunchTop, PlaceHolderQuickLaunchBottom<br />Add the Ribbon to page<br />Add additional controls to page<br />SPPageManager, ScriptManager, ScriptLink<br />Modify CSS classes based on your UI<br />
  25. 25. Upgrading themes<br />Old themes are not compatible with 2010<br />New themes files have to be created<br />Old themes can be used with legacy UI rendering mode before upgrade to 2010 UI is done<br />
  26. 26. Upgrade changed content<br />If SharePoint Designer has been used to customize site content, changed files are in database, not in file system<br />Two options<br />Reset the content to be in uncustomized state and provide updates using Feature Framework<br />Use SPD to manually update the changed files<br />
  27. 27. List view threshold<br />Queries that return/touch large numberof list items may fail. <br />Thresholds are configurable through the Central Administration site.<br />
  28. 28. Large List Considerations<br />This can bite you<br />Need it to surface in Development<br />Test as a non-admin user<br />Use realistic data volumes in development and test servers<br />Refactor code to use ContentIterator, if possible<br />
  29. 29. Using Existing Code <br />All SharePoint 2007 code in all processes will work without recompilation<br />Achieved by using machine level binding redirections<br />Binding redirections will work also for any custom code, which is not running under IIS<br />
  30. 30. just the wsp<br />demo <br />
  31. 31. Deprecated API's <br />Numerous API’s have been deprecated. <br />Recompile your application for 2010 and you will see warnings for any affected API’s within your application.<br />Deprecated doesn’t always mean unsupported!<br />Only affect will be a compiler warning<br />Most API’s deprecated in 2007 are still in 2010<br />Microsoft will not invest in these API’s in the future and will remove deprecated APIs after next version<br />
  32. 32. Deprecated API's Examples<br />SPFarm.Create<br />Message: Use the SPFarm.Create method that takes a passphrase.<br />SPVirtualServer<br />Message: Use SPWebApplication or SPIisSettings instead.<br />Shared Service Provider Code in some level<br />
  33. 33. Path and registry issues <br />Path to the SharePoint Hive has changed<br />C:Program FilesCommon FilesMicrosoft SharedWeb Server Extension14<br />Custom code that references 12 should be updated<br />Custom code references to 12 registry keys should be updated<br />
  34. 34. Other Issues<br />X86->x64 COM references (IID changes)<br />3rd party dependencies<br />HttpModule/HttpHandler registration changes for IIS7 integrated pipeline<br />
  35. 35. Other issues (cont)<br />
  36. 36. intranet upgrade<br />demo <br />
  37. 37. Upgrade logging<br />More logging information available<br />Actions conducted during psconfig upgrade are logged to dedicated logs <br />Logs located in the ULS folder<br />Improved logging and seperate error log<br />User interface on central administration application to view the upgrade actions<br />Provides additional information on the actions<br />
  38. 38. How to manage your upgrade process?<br />Managing your upgrade process<br />
  39. 39. Upgrade process<br />It’s much more than your customizations<br />Always use QA environments to verify the process<br />Preruns and document the possible issues and process to deploy<br />Virtualization provides excellent tools to move back to previous state<br />
  40. 40. Upgrade Cycle: Overview<br />
  41. 41. Summary<br />Upgrading VSeWSS project<br />Common upgrade issues for custom code<br />Issues you might run into during upgrade your code<br />Managing your upgrade process<br />What to consider during upgrade planning<br />Know your Tools<br />Whats available for FREE<br />Whenh yoiu should buy<br />
  42. 42.
  43. 43. Your Feedback is Important<br />Please fill out a session evaluation form.<br />Thank you!<br />Ivan Sanders<br /><br /><br /><br />
  44. 44. Who can you trust??<br />Maurice Prather<br />Andrew Connell<br />Spence Harbar<br />Heather Solomon<br />Todd Klindt<br />Todd Baginski<br />Todd Bleeker Tielens<br />Patrick Tisseghem<br />WictorWilen<br />Ted Patisson<br />Lars Fastrup<br />CarstenKeutmann<br />Keith Richie<br />Bill Baer<br />SahilMalik<br />BilSimser<br />
  45. 45. Codeplex – with Source Code<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
  46. 46. SharePoint 2010 Guidance<br />
  47. 47. CKS DEV VSIX Extensions<br />20<br />