With the new SharePoint Online being touted as the SharePoint platform for the future a number of organizations are planning to move to the cloud and leverage SharePoint online for collaboration and enterprise content management. One of the powerful features in SharePoint 2013 (and SharePoint online) is the new search engine. When you start working with SharePoint online you will encounter a number of differences between how on-premises SharePoint and SharePoint online are administered. One of these is how you work with Managed Properties.
While SharePoint 2010 supports .NET 3.5, it uses the .NET 2.0 compiler by default for ASP.NET pages. If you write any UserControls or consume any DLLs in your hosted ASPX pages that utilizes .NET 3.5 features such as the var keyword, extension methods, and LINQ, you’ll get compilation error messages when attempting to access those pages.
To resolve this issue, you can edit the web.config in your site collection’s virtual directory (Usually under \inetpub\wwwroot\wss\virtualdirectories\<site>). Add the following snippet under the configuration element:
<compiler language=”c#;cs;csharp” extension=”.cs” warningLevel=”4″
type=”Microsoft.CSharp.CSharpCodeProvider, System, Version=126.96.36.199,
Before You Read
Microsoft supports various upgrade paths from WSS3.0/MOSS 2007 to SharePoint 2010. This post will highlight the “attach and upgrade” approach.
Run the Pre-Upgrade Check on the SharePoint 2007 Server
Execute the following command from the command line on the SharePoint 2007 server hosting the database to be upgraded:
stsadm –o preupgradecheck
This will scan the server for potential problems that may cause errors during the upgrade process.
Review the log file to get specifics on any issues. The most likely cause will be features or customizations, so make sure that you uninstall any features or customizations that aren’t necessary on the new server.
Back Up Your 2007 Content Database
Back up your 2007 content database from SQL Management Studio on the SharePoint 2007 server, and put the backup file somewhere it is accessible from the new SharePoint 2010 Server instance.
Restore the 2007 Content Database…