Because of the downtime issues, in-place upgrades are better suited for small environments. In larger environments, the downtime needed to do an in-place upgrade may be too long. In-place upgrades may also not be suited for environments with significant custom code or other customizations. One of the benefits of an in-place upgrade is that the customizations in SharePoint 2007 are maintained. However, in order for your upgrade to be successful, your custom code must run in both SharePoint 2007 and SharePoint 2010.
Table below provides list of common customizations in SharePoint 2007 and recommendations on how to deal with them when upgrading to SharePoint 2010:
| Customization | Good Choice | Better Choice |
| Custom Web Parts | Probably work out of the box with SharePoint 2010 | Test on sample server, plan to rewrite for SharePoint 2010 |
| Custom event handlers | Probably work out of the box with SharePoint 2010 | Test on sample server, plan to rewrite for SharePoint 2010 |
| Custom Site template | Create a site with the Custom Site template before upgrade | Recreate in SharePoint 2010, preferably as a Solution package and Feature |
| Custom site definition | Create UDF file for upgrade | Migrate to an out-of-the-box site template and deploy customizations as a Solution package and Feature |
| Customized (unghosted) | Reset to site definition | Reset to site definition, and reapply customizations |
| Custom code or pages in /_layouts | Probably work out of the box with SharePoint 2010 | Test on sample server, plan to rewrite for SharePoint 2010 |
Posts
No comments:
Post a Comment