Visual Studio 2010 SP1 Readme

Date Published: May 3, 2011

For the latest version of the Readme, click here.

1. System Requirements

Supported Architectures:

Supported Operating Systems:

Hardware Requirements:

2. Known Issues

2.1. Installing

2.1.1. Visual C++ compiler installation fails when the Windows SDK 7.1 is installed, repaired, or modified after Visual Studio 2010 SP1 has been installed

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.

2.1.2. Visual Studio 2010 Service Pack 1 Setup cannot be run in Program Compatibility Mode

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.

2.1.3. Visual Studio 2010 Service Pack 1 installation may fail when a USB drive or other removeable drive is connected

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.

2.1.4. Visual Studio must be restarted after Visual Studio 2010 SP1 tooling for SQL Server Compact (Compact) 4.0 is installed

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.

2.1.5. Visual Studio 2010 SP1 Help Viewer experience is broken if "Help Viewer Power Tool" was installed on non-English versions of Visual Studio 2010 before SP1 is installed

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.

  1. Open QueryManifest.<version>.xml in \ProgramData\Microsoft\HelpLibrary\manifest\.
  2. Change all <brandingPackageFileName>dev10pt.mshc</brandingPackageFileName> entries to <brandingPackageFileName>dev10.mshc</brandingPackageFileName>.

    Save the changes.

  3. Install Visual Studio 2010 SP1. (The Power Tool will remain but will be ignored by SP1.)

Second Method: Uninstall the "Help Viewer Power Tool", and then install Visual Studio 2010 SP1:

  1. Open QueryManifest.<version>.xml in \ProgramData\Microsoft\HelpLibrary\manifest\.
  2. Change all locale-specific catalog entries, for example, <catalog productId="VS" productVersion="100" productLocale="JA-JP" productDisplayName="" sourceType="index"> to <catalog productId="VS" productVersion="100" productLocale="EN-US" productDisplayName="" sourceType="index">.
  3. Uninstall the Power Tool in the Programs section of the Control Panel.
  4. Change the locale tags in the Query Manifest back to their original locale designators.
  5. Change all <brandingPackageFileName>dev10pt.mshc</brandingPackageFileName> entries to <brandingPackageFileName>dev10.mshc</brandingPackageFileName>.
  6. Save the changes.

  7. Install Visual Studio 2010 SP1.

2.1.6. Microsoft SQL Server licenses are contained in files with abbreviated names

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 NameFull Product Name
SQL08AppFrame.rtfMicrosoft SQL Server 2008 R2 Data-Tier Application Framework
SQL08AppProj.rtfMicrosoft SQL Server 2008 R2 Data-Tier Application Project System
SQL08CLRtypes.rtfMicrosoft System CLR Types For SQL Server 2008 R2
SQL08SMO.rtfMicrosoft SQL Server 2008 R2 Shared Management Objects
SqlEv31Eula.rtfMicrosoft SQL Server Compact 3.5 with Service Pack 2
SQLServer2008_License_EXPR.rtfMicrosoft SQL Server 2008 Express Edition
sql08tsqllangsvc.rtfMicrosoft SQL Server Transact-SQL Language Service 1.1
Microsoft SQL Server Transact-SQL Language Service 1.1.rtfMicrosoft SQL Server Transact-SQL Language Service 1.1

2.1.7. The language version of the license file for Microsoft SQL Server Transact-SQL Language Service 1.1 is not correctly copied for German language installations

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. 

2.1.8. Extraneous entries for Visual C++ Standard hotfixes appear in Installed Updates List

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.

2.2. Uninstalling

2.2.1. If Visual Studio 2010 Service Pack 1 is uninstalled, Visual Studio 2010 must be reinstalled to restore certain components

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.

  1. Browse to the location from which you installed Visual Studio 2010.
  2. Run setup.exe. If you are prompted by User Account Control to elevate, click Continue.
  3. Click Change or Remove Microsoft Visual Studio 2010.
  4. When Setup is loaded, click Next.
  5. Click Add or Remove Features.
  6. Select the features you want to reinstall.
  7. Click Update.

2.2.2. If Visual Studio 2010 Service Pack 1 is uninstalled, Visual Studio 2010 must be reinstalled before SP1 can be installed again

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.

2.2.3. 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 is created

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.

2.2.4. Uninstalling Visual Studio 2010 SP1 removes Visual Studio Tools for Office and Visual Studio Tools for SharePoint features

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:

  1. In the Programs section of the Control Panel, right-click Microsoft Visual Studio 2010 and then click Uninstall\Change.
  2. In the Maintenance Mode dialog box, click Next and then click Add or Remove Features.
  3. Missing features have empty check boxes and a red "X" next to them. Select the the following features:
  4. Click Update. 

2.2.5. Uninstalling Visual Studio 2010 Service Pack 1 prompts for source for Express editions

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:

  1. Go to Express downloads on the Microsoft website.
  2. Download the ISO, which contains all versions of Express except for Windows Phone.
  3. Burn the ISO to a DVD. We recommend that you verify the media after the burn process completes.
  4. Open a Command Prompt window. (Click Start, click All Programs, click Accessories, and then click Command Prompt.)
  5. Change directories to the DVD drive, and then to the directory that corresponds to the product that is prompting for source. For example, if Visual C# Express is prompting for source, type: cd d:\vcsexpress (assumes that D: is your DVD drive).
  6. To find the file for the next step, type: dir ixp*.exe
  7. Using that file name, type: <file name>.exe /x:"%TEMP%\<file name>"
    For example: ixpvcs.exe /x:"%TEMP%\ixpvcs\"
  8. In the prompt for source dialog box, browse to the location where you extracted the files in step 7.
  9. Click OK to continue.

2.2.6. Uninstalling Visual Studio 2010 Service Pack 1 prompts for source

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:

  1. Locate the installation source that you used when you initially installed Visual Studio 2010.
  2. In the prompt for source dialog box, browse to the installation directory, select the MSI file, and click OK to continue.

2.3. Maintenance

2.3.1. Reinstalling Visual Studio 2010 Service Pack 1 may prompt for source

If you reinstall Service Pack 1, you may be prompted for a source.

To resolve this issue:

  1. Download the Visual Studio 2010 Service Pack 1 Setup application from http://go.microsoft.com/fwlink/?LinkId=209902. Save it in a location you will remember, for example, %USERPROFILE%\Downloads\.
  2. Open a Command Prompt window. (Click Start, click All Programs, click Accessories, and then click Command Prompt.)
  3. Type the following command to change directories to the location you saved in step 1: cd "%USERPROFILE%\Downloads"
  4. Type the following command to download all installation packages: setup.exe /createlayout "%CD%\VS2010SP1"
  5. In the prompt for source dialog box, find the MSI file for which you are prompted.

2.4. Product Issues

2.4.1. General Issues

2.4.1.1. Updated documentation for Visual Studio 2010 SP1 is not available for download until March 16, 2011

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.

2.4.1.2. Signing of managed assemblies for C++ applications that were converted before this Visual Studio 2010 SP1 release

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".

  1. Find the "KeyFile", "DelaySign" property in the "ItemDefinitionGroup" for "Link".
  2. <Link>

    <GenerateDebugInformation>true</GenerateDebugInformation>

    <AdditionalDependencies>

    </AdditionalDependencies>

    <KeyFile>my.snk</KeyFile>

    <DelaySign>true</DelaySign>

    </Link>

  3. Move these properties to the "PropertyGroup" of the corresponding Configuration/Platform.
  4. Change the "KeyFile" property to "LinkKeyFile".
  5. Change the "DelaySign" property to "LinkDelaySign".
  6. The modified property should resemble this:
  7. <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">

    <ConfigurationType>Application</ConfigurationType>

    <LinkKeyFile>my.snk</LinkKeyFile>

    <LinkDelaySign>true</LinkDelaySign>

    </PropertyGroup>

  8. If you have Custom build steps set to sign the binaries (as was recommended to fix the problem in the original release version),  you can remove them now.

2.4.2. Code Editor

There are no known issues.

2.4.3. Languages

2.4.3.1. Async CTP

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.

2.4.4. Visual Studio Tools for Office

There are no known issues.

2.4.5. SharePoint Development

2.4.5.1. In SharePoint Designer, creating a reusable workflow that has spaces in its name, exporting the workflow into a .wsp, and then using the 'Import Reusable WF' template to import it causes a build error

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

  1. Click 'Show all files' in Solution Explorer.
  2. Expand the 'Workflows' folder.
  3. Locate the <workflowname>.xoml.vb file and open it.
  4. Select the class name (including the spaces).
  5. Replace all instances of the class name with a name that does not have spaces. (Replace in the entire solution.)
  6. Build. There should be no build errors.

For C#

  1. Click 'Show all files' in Solution Explorer.
  2. Expand the 'Workflows' folder.
  3. Locate the <workflowname>.xoml.cs file and open it.
  4. Select the class name (including the spaces).
  5. Replace all instances of the class name with a name that does not have spaces. (Replace in the entire solution.)
  6. Build. There should be no build errors.

2.4.6. Web Development

There are no known issues.

2.4.7. Windows Communication Foundation (WCF) Tools

There are no known issues.

2.4.8. Windows Presentation Foundation (WPF) Tools

There are no known issues.

2.4.9. Windows Workflow Foundation (WF) Tools

There are no known issues.

2.4.10. Windows SDK Integration

There are no known issues.

2.4.11. Debugger, Database, Diagnostics and Analysis Tools

2.4.11.1. Installing Visual Studio 2010 SP1 breaks profiling for x64 applications on Windows Server 2003 x64

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.

2.4.12. Architecture Tools

There are no known issues.

2.4.13. Testing Tools

There are no known issues.

2.4.14. Lab Management Tools

There are no known issues.

2.4.15. Team Explorer

There are no known issues.

2.4.16. Setup Projects

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:

3. Related Links

3.1. Related Readme Files

Team Foundation Server 2010 SP1 Readme

Help Viewer 1.1 Readme

 

© 2011 Microsoft Corporation. All rights reserved.

Terms of Use | Trademarks | Privacy Statement