从2010年到2013年升级SharePoint与农场解决方案

Question

我正在使用SharePoint多版本。
我的一个客户要求从 SharePoint 2010（Foundation）升级到2013年。
我想知道以下：

1. 将SharePoint 2010到2013升级的步骤。
2. 对可能影响解决方案的现有系统的影响。
   1. 沙箱溶液
   2. 农场解决方案
   3. ootb solutions

      最重要的是我的工作流正在运行批准，并且有应用程序页，事件接收器和 search 可能会受到影响。
      如何处理所有这些方法。

      更新（2014年2月17日）：
      我有spd工作流程，也有视觉工作室工作流程。
      我有在Visual Studio中开发的应用程序页面。
      我有SPD表格（在2010年的SPD开发的自定义页面）。
      我有在Visual Studio 2010中开发的计时器工作和事件接收器。

Answer 1

Steps to Upgrade from SP 2010 to SP 2013: Make the site in SP 2010 readonly. Using SQL Management Studio, perform the backup of Content database and service database in SP 2010. Restore the databases in SP 2013 SQL server. Attach the content database to a site collection in SP 2013. Similarly, attach the service databse to the corresponding service in SP 2013. For more info please refer: http://sharepointnadeem.blogspot.com/2013/12/sharepoint-2013-upgrade-from-sharepoint.html

UPDATE

SharePoint 2010 workflows are supported in SP 2013 also. The only issue I faced while doing migration of SP 2010 site having workflows was about workflow activities:

The type or namespace name 'AssemblyName' could not be found (are you missing a using directive or an assembly reference?)". at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(SPWorkflowAssociation association, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association, Boolean fallback) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)
at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflo...

Opening the workflows associated with these lists from SharePoint Designer resulted in the error: Could not deserialize object. The type could not be resolved.

Resolution: Web.config files needs to be modified. For SharePoint 2010 custom activities to work in SharePoint 2013, the “authorizedType” node needs to be defined in a new sub-section “targetFx” under the “authorizedTypes” section.

I also had plenty of event recievers and they all worked very well.