Date Published: May 3, 2011
For the latest version of the Readme, click here.
If the Visual C++ Compilers checkbox is selected when Windows SDK 7.1 is installed, repaired, or modified after Visual Studio 2010 SP1 has been installed, the SDK installer attempts to install an older version of compilers. One of the following messages may be displayed:
or
To resolve this issue:
Condition 1: If the Visual C++ Compilers checkbox is selected when the Windows SDK 7.1 is installed, repaired, or modified after Visual Studio 2010 SP1 has been installed, the error may be encountered and some selected components may not be installed.
Workaround: Clear the Visual C++ Compilers checkbox before you run the Windows SDK 7.1 installation, repair, or modification.
Condition 2: If the Visual C++ Compilers checkbox is selected when the Windows SDK 7.1 is installed, repaired, or modified after Visual Studio 2010 has been installed but Visual Studio 2010 SP1 has not been uninstalled, the error may be encountered.
Workaround: Uninstall Visual Studio 2010 SP1 and then rerun the Windows SDK 7.1 installation, repair, or modification.
Visual Studio 2010 Service Pack 1 Setup fails with a 1603 (0x643) error code or blocks running in Program Compatibility Mode. Windows Program Compatibility Assistant indicates that Visual Studio Setup might not have installed correctly and prompts to reinstall it by using the recommended setting (Program Compatibility Mode).
To resolve this issue:
Visual Studio Setup cannot run in Program Compatibility Mode. Ensure that the Compatibility Mode setting is not enabled system-wide or for the Visual Studio Setup application.
Before you install or reapply Visual Studio 2010 Service Pack 1, disconnect all removeable drives. If this is not possible, do not remove any such drive while Setup is running because doing so may cause Setup to prompt for sources that it temporarily wrote to the drive (because it had more free space than other drives) or to fail completely because it cannot find the files.
To resolve this issue:
Either remove the drives before you install Visual Studio 2010 Service Pack 1 or do not remove them while Setup is running.
When a project that contains a Compact 4.0 .sdf file is opened and neither Compact nor Visual Studio Tools for SQL Server Compact 4.0 (Tools for Compact) is installed, Visual Studio 2010 SP1 asks whether the user wants to install the missing component. If the user says "yes," Web Platform Installer downloads and installs either Compact or Tools for Compact. However, if the user then tries to open the .sdf file, an "unknown error" occurs because Tools for Compact 3.5 is already loaded and it cannot be unloaded and replaced by Tools for Compact 4.0 until Visual Studio is restarted.
To resolve this issue:
Restart Visual Studio after you install the SQL Server Compact 4.0 tooling.
If "Help Viewer Power Tool" is installed on a non-English version of Visual Studio 2010 and then Visual Studio 2010 SP1 is installed, Help Viewer 1.1, which is installed with SP1, is not correctly configured and content may appear to be missing. When the "Help Viewer Power Tool" is installed on non-English Visual Studio 2010, changes are made to the QueryManifest.<version>.xml file. These changes must be reversed for Visual Studio 2010 SP1 to be successfully installed.
To resolve this issue:
There are two ways to address this issue:
First Method: Edit the Query Manifest without removing the "Help Viewer Power Tool", and then install Visual Studio 2010 SP1.
Change all <brandingPackageFileName>dev10pt.mshc</brandingPackageFileName> entries to <brandingPackageFileName>dev10.mshc</brandingPackageFileName>.
Save the changes.
Second Method: Uninstall the "Help Viewer Power Tool", and then install Visual Studio 2010 SP1:
Save the changes.
As stated in the License Terms, licenses for Microsoft SQL Server software components accompanying Visual Studio are located in the following directory: ..\Program Files\Visual Studio 10.0\Licenses\1033. Many of the licenses are provided with an abbreviated file name.
To resolve this issue:
For ease of use, a table of license file names and their respective full product name is provided.
License File Name | Full Product Name |
---|---|
SQL08AppFrame.rtf | Microsoft SQL Server 2008 R2 Data-Tier Application Framework |
SQL08AppProj.rtf | Microsoft SQL Server 2008 R2 Data-Tier Application Project System |
SQL08CLRtypes.rtf | Microsoft System CLR Types For SQL Server 2008 R2 |
SQL08SMO.rtf | Microsoft SQL Server 2008 R2 Shared Management Objects |
SqlEv31Eula.rtf | Microsoft SQL Server Compact 3.5 with Service Pack 2 |
SQLServer2008_License_EXPR.rtf | Microsoft SQL Server 2008 Express Edition |
sql08tsqllangsvc.rtf | Microsoft SQL Server Transact-SQL Language Service 1.1 |
Microsoft SQL Server Transact-SQL Language Service 1.1.rtf | Microsoft SQL Server Transact-SQL Language Service 1.1 |
Depending on setup choices, when installing a German language version of Visual Studio, a German language version of Microsoft SQL Server Transact-SQL Language Service 1.1 might also be installed. The correct license terms are displayed during setup, but the wrong language version of the license terms is copied to the folder ...\Program Files\Microsoft SQL Server\100\SDK\Assemblies\de.
To resolve this issue:
A hotfix has been issued to update your installation with the correct German language copy of the license terms for Microsoft SQL Server Transact-SQL Language Service 1.1. The hotfix can be obtained here.
The correct German language license can also be found in the Visual Studio License directory ..\Program Files\Visual Studio 10.0\Licenses\1031.
Visual Studio 2010 Service Pack 1 causes several entries to be created in the Installed Updates list. The entries are labeled “Hotfix for Visual C++ Standard 2010 Beta 1” along with a KB number. Microsoft confirmed that no Beta fixes are installed with Visual Studio 2010 Service Pack 1, and that each of the hotfixes listed are included in Visual Studio 2010 Service Pack 1.
To resolve this issue:
There is no workaround for this issue. No Beta 1 hotfixes are installed on your system. You cannot uninstall the updates or remove the entries from the Installed Updates list because no files are actually installed on your system.
Visual Studio 2010 Service Pack 1 upgrades some components of the Visual Studio 2010 original release version. If you uninstall Service Pack 1, some of these components are removed completely from the machine and not downgraded to their original versions.
To resolve this issue:
Reinstall the Visual Studio 2010 original release version from the original source media or network installation location. In Setup, select the features that you want to reinstall.
If Visual Studio 2010 Service Pack 1 is uninstalled, Visual Studio 2010 must be reinstalled before SP1 can be installed again.
To resolve this issue:
Read 2.2.1. in this readme for instructions about how to reinstall Visual Studio 2010 after SP1 is uninstalled. After Visual Studio 2010 is reinstalled, reapply SP1.
If Visual Studio 2010 SP1, SQL Server Compact runtime, and Visual Studio 2010 SP1 Tools for SQL Server Compact 4.0 ENU are installed, and then SP1 is uninstalled, an error may occur when a SQL Express database (.mdf) file is created.
To resolve this issue:
Repair the Visual Studio 2010 original release version and then uninstall the Visual Studio 2010 SP1 Tools for SQL Server Compact 4.0 ENU (SSCEVSTools-ENU.msi) by using the Programs section in the Control Panel.
Uninstalling Visual Studio 2010 SP1 removes the Visual Studio Tools for Office (VSTO) Design Time and Visual Studio Tools for SharePoint features. Because the Office and Sharepoint features in Visual Studio 2010 SP1 are major upgrades, they are removed when SP1 is removed and the earlier versions have to be restored in the Visual Studio 2010 original release version.
To resolve this issue:
When Service Pack 1 is uninstalled, files may have to be copied from the original source media for Visual Studio 2010 or related products. If the source cannot be found automatically, you will be prompted to supply a location. For Express editions, additional steps are required to re-download and expand the source.
To resolve this issue:
When Service Pack 1 is uninstalled, files may have to be copied from the original source media for Visual Studio 2010 or related products. If the source cannot be found automatically, you will be prompted to supply a location.
To resolve this issue:
If you reinstall Service Pack 1, you may be prompted for a source.
To resolve this issue:
You can use the Help Library Manager in Help Viewer 1.1 to download and install updated content from MSDN Online. Although updated documentation for Visual Studio 2010 SP1 is not available for download until March 16, 2011, it is available on the MSDN website.
To resolve this issue:
Access the Visual Studio 2010 SP1 documentation on the MSDN website now, and wait until March 16, 2011, to download it.
For information about how to download updated content, see "Getting Updates to Offline Content" in Help Library Manager (Microsoft Help System) on the MSDN website or in the Visual Studio 2010 documentation on your computer.
In C++ applications in the Visual Studio 2010 original release version, you could not sign the generated assemblies by setting Linker -> Advanced -> Delay Sign to "Yes". This problem has been fixed in Visual Studio 2010 SP1, but if the application is converted in the original release version before SP1 is applied, the project file must be modified manually.
To resolve this issue:
To modify your project file so that your assemblies can be signed when "Delay Sign" is set to "Yes".
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<AdditionalDependencies>
</AdditionalDependencies>
<KeyFile>my.snk</KeyFile>
<DelaySign>true</DelaySign>
</Link>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<LinkKeyFile>my.snk</LinkKeyFile>
<LinkDelaySign>true</LinkDelaySign>
</PropertyGroup>
There are no known issues.
If you installed the pre-SP1 version of Async CTP but did not uninstall it before you installed Visual Studio 2010 SP1, then your computer will be in a state in which the version of the C# compiler in the .NET Framework does not match the C# compiler in Visual Studio.
To resolve this issue:
After you install Visual Studio 2010 SP1, reinstall the SP1 version of the Async CTP from here.
There are no known issues.
If you create a reusable workflow in SharePoint Designer that has a name that contains spaces, export the workflow into a .wsp, and then import the workflow into Visual Studio by using the "Import Reusable Workflow" template, errors occur when you build the project.
To resolve this issue:
The class that is generated has spaces in it.
For Visual Basic
For C#
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
After Visual Studio Service Pack 1 is installed on Windows Server 2003 x64, profiling 64-bit applications fails and the "PRF0010: Launch Aborted - Unable to start vsperfmon.exe" message is displayed. This occurs because SP1 Setup breaks the registration of the 64-bit version of vsperfmon.exe.
To resolve this issue:
Install the Visual Studio 2010 Standalone Profiler SP1, which is available from MSDN. This fixes the registration of vsperfmon.exe and enables 64-bit applications to be profiled from Visual Studio.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
VCRedist SP1 packages have RTM Fwlinks that point to RTM packages. Users should be able to edit them in case they want to download correct SP1 packages
After installing VS SP1 patch, if the user adds VCRedist as a prerequisite to a setup project and chooses "home site" option, the setup project installation will download RTM VCRedist packages instead of SP1 VCRedist packages.
Generated ClickOnce manifests have RTM fwlinks that point to the RTM uploaded packages and not the SP1 packages.
To resolve this issue:
The user can manually edit VCRedist package.xml to replace the RTM fwlinks with the new SP1 fwlinks.
Package.xml should contain RTM fwlinks - e.g.
....
<String Name="VCRedistExe">http://go.microsoft.com/fwlink/?LinkID=177916&clcid=0x409</String>
...
The link in the above tag should be replaced with the following fwlink:
Team Foundation Server 2010 SP1 Readme
© 2011 Microsoft Corporation. All rights reserved.