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