This post lists and addresses known issues that developers have been frequently encountering while working with the Beta release of Microsoft SharePoint 2010. These issues relate only to the Beta versions of Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010, and are limited to areas that concern developers specifically. See Microsoft Office Servers Beta 2 Known Issues/ReadMe for a broader list of known issues with the Beta release of Office 14 server applications.
The issues listed here supplement the guidance and instructions provided in Setting up the Development Environment for SharePoint Server.
- When you install on Microsoft Windows 7 or Windows Vista, make sure that WCF HTTP Activation and WCF non-HTTP Activation are set. If these Windows Features are not set, the configuration wizard will fail at task 8. Step 2, item 8 in Setting up the Development Environment for SharePoint Server contains a command that you can use to enable all of the required Windows Features, including WCF HTTP Activation and WCF non-HTTP Activation. The command in that topic contains line breaks, however, so you will have to remove the line breaks manually before running it.
- Install the WCF hotfix. A hotfix that provides a method to support token authentication without transport security or message encryption in WCF is available for.NET Framework 3.5 SP1. Use this link for Windows Server 2008 and this link for Windows Server 2008 R2. The Windows Server 2008 fix also applies to Vista, while the Windows Server 2008 R2 fix also applies to Windows 7.
If you don’t have this fix installed, you will get an “Unrecognized attribute ‘allowInsecureTransport'” error in ULS log. And most of the service applications will not run properly. If you are installing on Windows 7 and have previously installed Visual Studio 2010, you may need to replace an installer file, as described in this blog post.
- If after installing SharePoint 2010 you are not getting ULS logs, either disable Windows Firewall or create an exception in Windows Firewall for WSSTracing.exe.
- We do not currently support installation on K or KN editions of Windows 7.
- Web Application Companions (WAC), SharePoint Search, and SharePoint User Profile Sync cannot be installed on Windows 7.
- When you create custom solutions with Visual Studio 2010, set the target framework to .NET Framework 3.5.
- When you add resources to a Mapped Folder in Visual Studio 2010, the default build action is set to Embedded Resource. If you do not set the build action to Content or None, the files in the Mapped Folder will not be included in the WSP.
- Deployment of BDC models with the Business Data Connectivity Model template in Microsoft Visual Studio 2010 does not yet work in SharePoint Foundation 2010. SharePoint Foundation is missing the feature event receiver that enables the import of BDC models. This does work in SharePoint Server, and before RTM Microsoft will release code for a feature event receiver that you can add to your BDC projects to deploy to SharePoint Foundation.
- References to assemblies in “*\14\Templates\Layouts\ClientBin” (including Microsoft.SharePoint.Client.Silverlight.dll and Microsoft.SharePoint.Client.Silverlight.Runtime.dll) result in paths that are too long for Visual Studio 2010. Andrew Connell describes this problem and proposes a work-around in this blog post.
- Sites created from SharePoint Designer 2010 do not have the AssociatedOwnerGroup property of SPWeb set by default. As a result, site owners cannot complete workflow tasks that are not assigned to them. When they try to do this, they receive error messages indicating that that workflow tasks were rolled back because the users do not have the correct permissions. Workflows use the AssociatedOwnerGroup property to determine who can override the rollbacks. To fix this, set the AssociatedOwnerGroup property with code, or create a new site from the browser.
- Some assemblies, such as Microsoft.SharePoint.Publishing, appear in some cases to have a dependency on an incorrect version of the System.Web.DataVisualization assembly. The incorrect reference causes build failures. If you see this problem, add a reference to the correct version of System.Web.DataVisualization on your system. If your installation is on the C drive, that assembly will be located here:
C:\Program Files (x86)\Microsoft Chart Controls\Assemblies\System.Web.DataVisualization.dll
- If you install or upgrade a custom solution built on Microsoft Office SharePoint Server 2007 that embeds the SearchBoxEx Web Control into your custom master page, you will get an error indicating that “the type or namespace name ‘SearchBoxEx’ does not exist in the namespace ‘Microsoft.SharePoint.Portal.WebControls’.” This will not happen if you simply add the Search Box Web Part to a Web Part page. This will be fixed in the RTM version. You can work around this issue by updating your customized master page to include this tag:
<%@ Register Tagprefix=”MSSWC” Namespace=”Microsoft.SharePoint.Portal.WebControls” Assembly=”Microsoft.Office.Server.Search, Version=22.214.171.124, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
Once you have added this tag, you can then embed the SearchBoxEx Web Control with this tag:
The <SPSWC:SearchBoxEx id=”SearchBox”…> tag should also work as long as the Web form has been registered to use the Microsoft.SharePoint.Portal.WebControls namespace in the Search assembly.
- If you are testing your installation with Internet Explorer on your server machine, turn off IE Enhanced Security Configuration in your Server Manager. This will make certain site operations, such as “New|Edit” dialogs, work more smoothly.