Visual Studio 2010 Readme

For the most current version of the Readme, click here.

1. System Requirements

1.1 Supported Architectures

1.2 Supported Operating Systems

1.3 Hardware Requirements

2. Known Issues

2.1 Installing

2.1.1 Crystal Reports requires a separate installation for Visual Studio 2010

For Visual Studio 2010, Crystal Reports is a separate download and installation.  Creating Crystal Reports projects or Web sites or importing existing projects or Web sites that were created by using an earlier version of Visual Studio or Crystal Reports requires a Visual Studio 2010-compatible version of Crystal Reports to be installed.

To resolve this issue:

If Crystal Reports are used with Visual Studio 2010, use the Crystal Reports link in the Related Links section of this Readme to download and install a Visual Studio 2010-compatible version of Crystal Reports. This installation will enable the creation of Crystal Reports projects and Web sites and also enable the upgrade of existing projects and Web sites to work with Visual Studio 2010.

2.1.2 Visual Studio reports Package Load Failure for "FSharp.ProjectSystem.dll" on first run and when F# features are used

If the "Microsoft Visual F# 2.0 Runtime" was installed before "Microsoft .NET Framework 4" was installed, and then "Microsoft Visual Studio 2010" is installed on a system, the setup will appear to succeed, but F# components will not be correctly installed.  This will cause possible Package Load Failure errors related to "FSharp.ProjectSystem.dll", during the initial run of the "Choose a profile..." dialog box, and then whenever F# features are used in Visual Studio 2010.

To resolve this issue:

  1. In Add/Remove Programs, select "Microsoft Visual F# 2.0 Runtime" and click "Uninstall".  Follow the directions to uninstall the F# redist.
  2. In Add/Remove Programs, select "Microsoft Visual Studio 2010 <your SKU and language>" and click "Uninstall/Change...". 
  3. In Add/Remove Programs, select "Micro3) In Add/Remove Programs, select "Microsoft Visual Studio 2010 <your SKU and language>" and click "Uninstall/Change...". 

2.1.3 Visual Studio 2008 breaks after the .NET Framework 4 is uninstalled

If Visual Studio 2008 is installed, then Visual Studio 2010 is installed, and then the .NET Framework 4 is uninstalled (or both Visual Studio 2010 and the .NET Framework 4 are uninstalled), when you try to load a project on Visual Studio 2008, you get this error:
“Unable to read the project file ‘Project.proj’. MSBuildToolsPath is not specified for the ToolsVersion “4.0” defined at “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0”, or the value specified evaluates to the empty string.”

This problem might occur because the Windows SDK v7.0A, or some of the registry keys that it uses, are still present on the computer.

To resolve this issue:

  1. Make sure that Visual Studio 2010 is completely uninstalled (in “Control Panel -> Programs -> Programs and Features”, make sure Visual Studio 2010 is not listed).
  2. Make sure the following registry keys do not exist on the computer:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\4.0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersion\4.0

If you are working on a 64-bit operating system, delete these keys from the 32-bit part of the registry. To do this, click “Start -> Run”, type %WinDir%\SysWOW64\regedit.exe, and then make the registry changes.

Visual Studio 2008 should now be fully functional.

2.1.4 Visual Studio may be installed with an expired trial license

Installing Visual Studio 2010 with a trial license on a computer that previously had Visual Studio 2010 Ultimate LCTP (March 2010) or a release version of Visual Studio 2010 in trial mode may display a message that the evaluation period has expired.

To resolve this issue:

Visual Studio 2010 release provides one trial period.  After the original trial license is expired (30 or 90 days from the original installation), re-installing will not activate a new evaluation period.  Enter the full official product key to unlock the product.

2.1.5 Additional languages of the Silverlight 3 SDK will not be installed if a build of the Silverlight 3 SDK is already installed

If a version of the Silverlight 3 SDK is already installed, additional languages of the Silverlight 3 SDK will not be installed by Visual Studio 2010.

To resolve this issue:

Additional languages of the Silverlight 3 SDK can be downloaded from http://go.microsoft.com/fwlink/?LinkID=157102 and installed side-by-side with other Silverlight SDKs.

2.1.6 Repair of Visual Studio 2010 does not install Visual Studio Macro Tools if they failed to install during the Visual Studio installation, or were uninstalled

Repair of Visual Studio 2010 does not repair or install Visual Studio Macro Tools when they were never installed, or were uninstalled.

To resolve this issue:

  1. On the Add or Remove programs page, select Uninstall/Change Visual Studio 2010 and then click Next.
  2. Select Add or Remove features.
  3. Clear and then re-select any of the features in the list.  This causes the update state to be enabled.
  4. Finish the Setup wizard. Visual Studio Macro Tools should be installed.

2.1.7 On computers on which Visual Studio 2008 or SQL Server 2008 is installed and Visual Studio 2010 has been uninstalled and then reinstalled, using the Visual Studio Macros IDE may cause Visual Studio to crash

Uninstalling Visual Studio 2010 also removes the Visual Studio Macro Tools package. If the computer also has Visual Studio 2008 or SQL Server 2008, then reinstalling Visual Studio 2010 does not reinstall the Visual Studio Macro Tools package. This causes an error when the Macros IDE is started, and Visual Studio crashes if you try to recreate the MyMacros.vsmacros project.

To resolve this issue:

  1. Delete the following file:
  2. On the Add or Remove programs page, select Uninstall/Change Visual Studio 2010 and then click Next.
  3. Select Add or Remove features.
  4. Clear and then re-select any of the features in the list.  This causes the update state to be enabled.
  5. Finish the Setup wizard. Visual Studio Macro Tools should be installed.

2.1.8 Visual Studio SharePoint projects that target SharePoint 2010 have specific installation requirements

To work with SharePoint projects in Visual Studio 2010, the following components must be installed:

To resolve this issue:

There is no workaround for this issue.

2.1.9 Visual Studio Office projects that target Office 2007 or Office 2010 have specific installation requirements

To work with Office projects in Visual Studio 2010, the following must be installed:

To resolve this issue:

There is no workaround for this issue.

2.1.10 Visual Studio Setup cannot be run in Program Compatibility Mode

Visual Studio 2010 and/or the .NET Framework 4 Setup fails with 1603 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 the user to reinstall 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.

Check the manual setting

Compatibility mode could have been set manually on the Compatibility tab on the executable file properties.

  1. On the Visual Studio Setup media, locate setup.exe.
  2. Right-click setup.exe and then click Properties.
  3. On the Compatibility tab, clear "Run this program in compatibility mode for" and then then click OK.

Check Program Compatibility Assistant registry settings

Compatibility mode could have been set by Program Compatibility Assistant on earlier failed or canceled attempts to run Visual Studio setup.exe.

  1. Click Start, and then click Run.
  2. Type regedit, and then click OK.
  3. Browse to each of the following keys and delete any value that refers to setup.exe in the Visual Studio install path:

Rerun Visual Studio Setup

  1. Open Windows Explorer.
  2. Browse to Visual Studio setup.exe.
  3. Double-click setup.exe to run Visual Studio Setup.

Related KB Article

http://support.microsoft.com/kb/931709

Another Workaround:

Instead of executing the <DVD ROOT>\setup.exe, execute <DVD ROOT>\setup\setup.exe

2.1.11 Visual Studio 2010 fails to install on a BitLocker-enabled hard disk when Protection is On

When a user executes a setup process to install to a BitLocker-enabled disk, the process will fail if the disk is locked.

To resolve this issue:

Suspend Protection on the BitLocker-enabled disk before Visual Studio 2010 is installed. After Visual Studio 2010 installation is complete, resume Protection on the BitLocker-enabled disk.

Alternatively, avoid this issue entirely by preinstalling the .NET Framework 4 and Windows Installer 4.5 by following the Avoiding Restart during Setup steps.

2.1.12 Important System Updates to keep on your computer when uninstalling Visual Studio 2010

Visual Studio 2010 may install important system updates.

To resolve this issue:

We recommend keeping the following updates on your system after Visual Studio is removed:

2.1.13 Roaming profiles are only supported if they are used for the offline scenario

If Roaming profiles are used when the home folder is disconnected from the network, Setup will fail because folder redirection issues are caused by the way that Windows Installer installs products.

To resolve this issue:

If Roaming profiles are used when the home folder is disconnected from the network, Setup will fail because folder redirection issues are caused by the way that Windows Installer installs products.

To resolve this issue:

Configure your Roaming profiles to use the local path instead of the remote connection path, or ensure that the remote home folder path is available during installation.

To switch to local profile, following these steps:

On the domain server:

1. Set roaming profiles for the targeted user (for example, myuser), as follows:

Right-click user myuser in the Active Directory (AD), and then click Properties. On the "Profile" tab, in the Profile path, type a UNC path that resembles \\domainserver\Rprofiles\%username% (for example, \\10.50.209.130\Rprofiles\myuser). Note: "\\domainserver" is the AD server IP, "\Rprofiles" is the new folder that will store all user roaming profiles, "\username" is the user (myuser in this example) logon name.

2. Set the home folder for the targeted user, as follows:

Local path for home folder:

Select Local path, type a local path that resembles c:\Rprofile, which will be created in the client for the user (myuser). Do not use a UNC path.

On the client computer:

  1. Log on the client as administrator and add to the Administrator Group the current user that was created on the AD server (myuser in this example).
  2. Create  the local path by using the path that was used in step 2 of the domain-server procedure (c:\Rprofile in this example).
  3. Log on the client as the new user (myuser in this example).
  4. Log off the client after the first logon. The local profiles will be saved automatically to the roaming profiles path in the server, that is \\domainserver\Rprofiles\%username% (for example, \\10.50.209.130\Rprofiles\myuser).
  5. Go back to the domain server and open the user folder (c:\Rprofiles). Notice that there is a new folder (c:\Rprofiles\myuser) and many files in the folder. These files are the roaming profiles. They are synchronized automatically with the user folder on the client on logoff.

2.1.14 Visual Studio installation fails because a .cab file has an invalid digital signature, when a network is involved

Network issues occasionally cause corrupted files when the files are downloaded and then installed, or when the files are installed over the network.  This issue manifests itself by a message in the %temp%\dd_install*.log that resembles this:

[05/16/09,17:47:12] VC 10.0 Runtime (x86): MSI Record result detail: Error 1330.A file that is required cannot be installed because the cabinet file e:\dev10dvd\wcu\vcruntimes\x86\vc_runtime_x86.cab has an invalid digital signature.  This may indicate that the cabinet file is corrupt.

[05/16/09,17:47:12] VC 10.0 Runtime (x86): MSI Record result detail error code: 1330

[05/16/09,17:47:13] InstallReturnValue: GFN_MID Chained VC Runtime 2010 Beta1 x86, 0x643

To resolve this issue:

Download the installation locally, verify the CRC, and then restart the installation.

2.1.15 NetBook installing with too low resolution

When Visual Studio 2010 is installed on a Netbook, the navigation buttons at the bottom of the dialog box cannot be seen.

To resolve this issue:

Check your display resolution to ensure that the minimum required resolution is being used:

To do this on Windows XP:

To do this on Windows Vista or Windows 7:

2.1.16 Do not unplug temporary drives during Setup

When Visual Studio 2010 is installed, and the USB drive is unplugged, then your installation might either prompt for source or fail to install due to missing temporary files.

To resolve this issue:

Either unplug all USB Drives before installing Visual Studio or do not unplug these drives during Setup because some temporary files do get copied and used on the drive that has the largest amount of freespace.

2.1.17 Visual Studio ISO should not be mounted as directory on existing NTFS drives

Mounting Visual Studio Setup media ISO as NTFS Path in Windows Disk Management may cause Setup to report missing write permissions to the destination folder or not enough disk space.

To resolve this issue:

Use any of the following methods to provide access to Visual Studio Setup ISO resources:

Re-run Setup from the new virtual drive location.

2.1.18 Error when a component is installed during installation of Visual Studio: MSI Record result detail error code: 1935

When Visual Studio is being installed, a failure in the installation of a component causes the following line in the logs:

...: MSI Record result detail error code: 1935

To resolve this issue:

Error 1935 has many causes, but is typically the result of the inability to overwrite a file.  This could be because the file is in use by some other application, in which case rebooting and restarting the Visual Studio installation should correct the problem.

Another common case is anti-virus software, which locks the newly-copied file to check it for malware.  Disabling anti-virus protection for the duration of the installation should enable installation to continue.

2.1.19 Error when Visual Studio is being installed from an ISO image mounted as a drive or folder

When Visual Studio is being installed from an ISO image mounted either as a drive or as a folder, it may fail with a wide variety of error messages.  These errors may include:

To resolve this issue:

These problems may be avoided by burning the ISO image to a DVD and then starting Setup from the actual DVD.

2.1.20 Cannot create any Visual Studio project if MSXML6 is not installed

If MSXML6 is not installed, the initial profile selection dialog box may not be displayed, and when projects are created, error messages that resemble this one may appear:

"Error writing the project file. Class not registered."

To resolve this issue:

  1. Install MSXML6 from MSDN: http://www.microsoft.com/downloads/details.aspx?FamilyID=993C0BCF-3BCF-4009-BE21-27E85E1857B1&displaylang=en.
  2. Restart Visual Studio.

2.1.21 Windows XP x64 is not supported because Windows Automation API 3.0 is missing

Applications that leverage Windows Automation APIs, for example, the Windows pen and touch services, can slow Visual Studio IntelliSense performance if the 3.0 version of the Windows Automation APIs is not installed. Windows Automation API 3.0 is not available for Windows XP x64.

To resolve this issue:

Use an operating system that supports Windows Automation API 3.0.

2.1.22 Windows Phone Developer CTP is not compatible with Visual Studio 2010

Windows Phone Developer CTP is not compatible with Visual Studio 2010.  Computers that have or previously had Visual Studio 2010 RTM installed will not be able to run CTP version of Windows Phone Developer.

To resolve this issue:

Uninstall Windows Phone Developer CTP and then install Beta or RTM versions of that product.

2.2 Uninstalling

2.2.1 On machines with previous versions of Visual Studio

2.2.1.1 When multiple copies of Visual Studio 2010 are installed on the same computer, uninstalling one of them will break Office and SharePoint Development

When multiple copies of Visual Studio 2010 are installed on the same computer, uninstalling one of them will break Office and SharePoint Development.

To resolve this issue:

  1. In the control panel, open add/remove programs.
  2. Right-click any remaining copy of Visual Stuido 2010 and select repair.  This will open the repair dialog box.
  3. Click the cusotmize setup radio button and click next.
  4. In the customize seutp, toggle any of the check boxes and click next.
  5. Setup will continue and reinstall the Office and SharePoint components.

2.2.1.2 Visual Studio 2010 uninstall instructions

All pre-release versions of Visual Studio 2010 must be removed before the official release version is installed.  Uninstalling official release versions of Visual Studio 2010 removes core product features only, and leaves other supported products that may have been originally installed with Visual Studio on the computer.

To resolve this issue:

For complete steps, see the uninstall documentation on MSDN at http://go.microsoft.com/fwlink/?LinkID=151208.

2.2.2 On machines with no previous versions of Visual Studio

2.2.2.1 On a 64-bit computer, uninstalling Visual Studio Ultimate will remove TraceLogProfiler.dll from the computer even if there is another product depending on it

TraceLogProfiler.dll is installed with the following Visual Studio SKUs:

If one of the SKUs is uninstalled, TraceLogProfiler.dll will be removed from the computer and will prevent IntelliTrace and Test Impact data from being collected in the other SKUs.

To resolve this issue:

Uninstall and then reinstall the Test Elements or Test Agent SKU to replace the missing binary.

2.3 Maintenance

2.3.1 How to add or remove components in Visual Studio 2010

After Visual Studio is installed, components that were not installed by default can be added, follow these steps to add them.

To resolve this issue:

To install optional components on Windows XP or earlier

To install optional components on Windows 7 or Windows Vista

2.3.2 How to repair Visual Studio

If Visual Studio becomes unstable, put it back into a known state by repairing it.

To resolve this issue:

For complete steps, see the Visual Studio repair documentation on MSDN.

2.3.3 Reinstalling missing companion products, which are not shown in the Add/Remove features

If a product has been uninstalled, which is required for some functionality and was installed by the Visual Studio 2010 original release, this component might not have been shown in the Setup customization tree nor in the Add/remove features tree.  How do you get this component back?

To resolve this issue:

  1. Open Add/Remove features or uninstall programs.
  2. Open Microsoft Visual Studio 2010 program.  
  3. On the "Maintenance page", click "Add or Remove Features".
  4. On the "Options" page, find the feature that is related to the missing feature. For example, if Web Deployment Tools are missing, then toggle the Web Deployment Feature on and off again.
  5. Click Update.  This will determine that the Web Deployment Tools companion product is not installed and will attempt to install it.
  6. Click Finish on the "Finish" page.

2.4 Product Issues

2.4.1 General Issues

2.4.1.1 Support for Business Intelligence Projects

Visual Studio 2010 does not support Business Intelligence projects from SQL Server 2008 R2 or earlier. In Visual Studio 2010, if a project is upgraded that is created in Business Intelligence Development Studio, the upgrade will not succeed. Business Intelligence Development Studio for Visual Studio 2010 is currently under consideration for future releases of SQL Server.

To resolve this issue:

No workaround is available.

2.4.1.2 "Improve Visual Studio Performance" notification

Applications that use Windows Automation APIs, for example, the Windows pen and touch services, may slow Visual Studio IntelliSense performance if the 3.0 version of the Windows Automation APIs is not installed. If Visual Studio detects that Windows Automation APIs are being used and the 3.0 version is not installed, the "Improve Visual Studio Performance" notification is displayed.

To resolve this issue:

  1. To download the 3.0 version of the Windows Automation APIs, click the link in the notification and then follow the instructions. (See KB981741.)
  2. Customers who cannot install the update can set the following registry key to prevent the notification from being displayed:

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\General]

"UIAOverride"=dword:00000001

2.4.1.3 Help Library Manager cannot download content from the cloud when the current user and the logged-in user are different

Help Library Manager (HLM) uses the BITS service to download content. If HLM is launched by using the "Run as" feature, BITS will not be able to schedule jobs because the service is available only to the logged-on user account.

To resolve this issue:

When content is downloaded, run HLM under the user account that is currently logged on.

2.4.1.4 Help Library Manager - Help content is not uninstalled when Visual Studio is uninstalled

Setup does not remove local help content when Visual Studio is uninstalled. The default location for the local content directory changed between Beta 2 and this release.

To resolve this issue:

If Visual Studio has already been uninstalled, the files can be manually deleted in the local help content directory. If the Beta 2 local help content directory was not used the Beta 2 content directory must be deleted manually to remove it from your computer.

2.4.1.5 The offline Help Viewer search button and the code snippet tabs might not be clickable

On Windows Server 2008 systems that have Internet Explorer running with restricted permissions, the offline Help Viewer search button and the code snippet tabs might not be clickable.

To resolve this issue:

127.0.0.1 can be added to the Internet Explorer trusted sites. Alternatively, for the search button issue, press ENTER to perform the search.

2.4.1.6 Help Library Manager running on Windows XP shows incorrect error message when a UNC path is specified for the content store

When Help Library Manager (HLM) is run on Windows XP, and the local content store is set to a UNC path (path that starts with \\), HLM displays a misleading error message.  When HLM checks that the local store directory is a valid and writeable location, it incorrectly reports that the  UNC path is a system directory. This causes HLM to display a misleading error message.

To resolve this issue:

There is no workaround for this issue.

2.4.1.7 Help Library Manager - Local content store path cannot include the "#" character

When Help Library Manager is run for the first time, a prompt for the location where local content will be stored will be shown. This folder path cannot include a "#" character. If the path includes the character, the Help Library Agent will not be able to render the content.

To resolve this issue:

There is no workaround for this issue.

2.4.1.8 Help Library Agent - closing the "Invisible" window causes the Help Library Agent to stop working

A window titled "Help Library Agent Invisible Window" can become visible. If the window is closed, the Help Library Agent will stop responding.

To resolve this issue:

Use Task Manager to end the agent process. It will restart itself when Help is restarted by using the shortcut, Help menu item, or F1.

2.4.1.9 Three project locations for loading templates are migrated when a Visual Studio 2008 settings file is loaded

When your user data is reset and import a Visual Studio 2008 settings file, the contents under Projects and Solutions in the Options dialog box display incorrect values.

To resolve this issue:

  1. Open the the Options dialog box.
  2. Select the Projects and Solutions node.
  3. Manually change the Projects location, User project templates location, and User item templates location to the correct path.
  4. If necessary, remove the extra "1" at the end.

2.4.1.10 Add-in fails to run with Error 80004002 (No such interface supported)

In an add-in, when <Assembly: ComVisible(True)> is modified to <Assembly: ComVisible(False)> the add-in fails to load.

To resolve this issue:

This is not supported because add-ins are built on top of a COM infrastructure and, although the add-in is written in managed code, the assembly ComVisible attribute must still be set to true.

2.4.1.11 An add-in that targets a version of the .NET Framework that is earlier than the .NET Framework 4 will display warnings at build time

When an add-in is created and the Framework target is changed to a version that is earlier than the .NET Framework 4, build warnings will occur.  This happens because additional references are added for the .NET Framework 4 support.

To resolve this issue:

Remove the following references from your add-in project:

2.4.1.12 Creating a template for a Web project or Web item does not put the template in the Web node in the New Project dialog box or the New Item dialog box

When a template for a VSIX project or item that targets the Web is built, the template will not appear correctly in the New Project dialog box or the New Item dialog box unless the template is put in a specific directory.  If the directory structure in the VSIX is incorrect, the template may appear at the root of CSharp or VB.

To resolve this issue:

  1. Put the template compressed file under ...\Template\CSharp\Web\ or ...\Template\VB\Web\, relative to the root of your VSIX file.
  2. In your source.extension.vsixmanifest file, add a reference that points to the compressed file.

2.4.1.13 Unable to use Createpkgdef to generate a .pkgdef file from registration attributes

SolutionPersistenceRegistrationAttribute code must be added to your project before the attribute can be used.

To resolve this issue:

If the SolutionPersistenceRegistrationAttribute class is used in your code when a .pkgdef file is autogenerated, the code in the MPF Sources in your Visual Studio SDK installation must be added. The source is located in the Visual Studio SDK installation folder under ..\VisualStudioIntegration\Common\Source\CSharp\RegistrationAttributes\SolutionPersistenceRegistrationAttribute.cs.

2.4.1.14 Users may experience reduced performance when running Visual Studio 2010 on Windows Server 2008 and Windows Server 2008 R2 with the HyperV role installed

Visual Studio switches from hardware-accelerated rendering to software rendering when it runs in virtualized environments.  Installing the HyperV role causes Visual Studio to fail to detect the correct rendering settings.

To resolve this issue:

To manually enable hardware-accelerate rendering:

  1. Open the Options dialog box.
  2. Under Environment, on the General page, in the "Visual experience" group, clear the "Automatically adjust visual experience based on client performance" option.
  3. Select "Use hardware graphics acceleration if available".
  4. Click OK.

2.4.1.15 Visual Studio SDK: Cannot Include Miscellaneous Files in a Visual Studio Project Template or Item Template

Miscellaneous files added to a Visual Studio project-template project or item-template project are not included in the compressed file generated during the project build.

To resolve this issue:

For every file included in your project, set the BuildAction to "ZipItem". This will generate in your bin directory a custom compressed file that contains all the required files.

2.4.1.16 Converting a Visual C++ Visual Studio Add-in Project Causes the Build Error: "error C2871: 'Extensibility' : a namespace with this name does not exist"

When a VC++ Add-in project is converted to Visual Studio 2010, building the converted project may cause the following error:

error C2871: 'Extensibility' : a namespace with this name does not exist

This build error is caused by a missing reference to the shared assembly that is located at %ProgramFiles(x86)%\Common Files\microsoft shared\MSEnv\PublicAssemblies\extensibility.dll after the conversion.

To resolve this issue:

  1. Right-click your add-in project and click References.
  2. In the References section of the dialog box, click Add New References.
  3. Select the Browse tab of the Add Reference dialog box. 
  4. Navigate to %ProgramFiles%\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\, select extensibility.dll, and click OK.Rebuild the project.

2.4.1.17 Extension Manager license-agreement dialog box shows extra blank space

The license-agreement dialog box in Extension Manager may contain extra white space when it shows a text license.  The dialog box renders every carriage return and every line feed character as a new line; this creates extra blank lines when a licence agreement is rendered.

To resolve this issue:

These formatting issues can be fixed by regularizing the whitespace.  To do this in the Visual Studio editor:

  1. Open your file in the text editor.
  2. Edit -> Find and Replace -> Quick Replace.
  3. Find options -> Use -> Regular Expressions.
  4. Find what: \xD\xA
  5. Replace with: \xD
  6. Click Replace All.

2.4.1.18 WPF Toolbox Controls created by using the Visual Studio SDK can cause Visual Studio to hang if spaces are included in the project name

If the Visual Studio SDK is used to generate a WPF toolbox control, and spaces are used in the project name, the file name of the assembly that is generated will also contain spaces. 

This can cause instability with the control in the WPF designers and the Toolbox.

To resolve this issue:

  1. Right-click your project in Solution Explorer and click "Properties".
  2. In the Assembly Name  field, remove all space characters.
  3. Rebuild.

2.4.1.19 Isolated Shell "New File" dialog box contains incorrect items when it is run from SDK template

By default, the File -> New -> File dialog box is configured to look in the same directory as the Visual Studio installation. In your Isolated Shell application, this dialog box can be configured to look in a different folder.

To resolve this issue:

  1. In your Isolated Shell solution, locate and open the <SolutionName>.Application.pkgdef file under the Shell Customization project folder for the startup project.
  2. Append the following text to this file, and replace  <NewDirectory> with a subdirectory in your application's protected installation location:

[$RootKey$\Projects\{A2FE74E1-B743-11d0-AE1A-00A0C90FFFC3}\AddItemTemplates\TemplateDirs\{DA9FB551-C724-11d0-AE1F-00A0C90FFFC3}\/1]

"TemplatesDir"="<NewDirectory>"

[$RootKey$\Projects\{2150E333-8FDC-42A3-9474-1A3956D46DE8}\AddItemTemplates\TemplateDirs\{DA9FB551-C724-11d0-AE1F-00A0C90FFFC3}\/1]

"TemplatesDir"="<NewDirectory>"

2.4.1.20 Project-to-project references are ignored by VSIX project

If a project is added in your solution by using the "Add Content"  feature in a VSIX project, the projects that it references are not included in the generated VSIX.  The VSIX project will only include content and files from its own set of project references.

To resolve this issue:

For each missing project-to-project reference:

  1. Right-click the VSIX project, and click "Add References".
  2. Add a reference to the missing project or file included in the generated VSIX.

2.4.1.21 Help Library Manager - Pressing the "Install Documentation" button at the end of Visual Studio Setup appears to have no effect

Pressing the "Install Documentation" button runs the Help Library Manager, which is the application that installs local help.  Help Library Manager first prompts for a local content location. This prompt is displayed in a dialog box that might not appear in front of the Visual Studio Setup window.

To resolve this issue:

Complete the Visual Studio installation to close the Setup window, or minimize the Setup window.

2.4.1.22 Cannot migrate Visual Studio 2008 VC++ directories to Visual Studio 2010 when devenv /useenv is used

When devenv /useenv is used in Visual Studio 2010, VC++ directories settings from Visual Studio 2008 cannot be migrated from the .vssettings file.

To resolve this issue:

If you want to migrate Visual Studio 2008 settings, run Visual Studio 2010 by using "devenv" instead of "devenv /useenv".

  1. Run devenv.
  2. Migrate Visual Studio 2008 VC++ directories from attached .vssettings file.
  3. Close devenv.

2.4.1.23 "Inherited Project Property Sheets" property from Visual C++ projects has been removed

"Inherited Project Property Sheets" property from Visual C++ projects has been removed.

To resolve this issue:

Use property manager to add/remove property sheets to the project. To view property manager, click "View -> Property Manager" in the IDE.

2.4.1.24 Managed Incremental Build for Visual C++ projects is not supported

Managed Incremental Build for Visual C++ managed projects is not supported in Visual Studio 2010.

To resolve this issue:

There is no workaround.

2.4.1.25 When a new x64 platform is created from the Win32 platform for C++ projects, the TargetEnvironment property is not correctly copied

When a new x64 platform is created from the Win32 platform for C++ projects, TargetEnvironment property is not correctly copied. This may cause link errors.

To resolve this issue:

  1. Right-click the project.
  2. Bring up property pages for the project.
  3. Go to "Link->Advanced".
  4. Change property "Target Machine" to "Machine X64 (/MACHINE:X64)".

2.4.1.26 C++ Include paths (VC++ Directories) get imported in different order, sometimes causing build breaks

When native C++ include paths are imported from Visual Studio 2008, the user paths forcibly go before the SDK paths. That prevents applications from being built if some header file names overlap.

To resolve this issue:

  1. Open property manager by clicking View.Property Manager.
  2. Expand the project node and then the configuration|Platform nodes, notice that there is "Microsoft.cpp.<Platform>.users" file for each configuration|Platform. These are the files for the global settings, and they resemble the old tools/Options/VC++ Directories.
  3. Select all the "Microsoft.cpp.<Platform>.users" files, and right-click to bring up the property page window.
  4. In the property page window, click "VC++ Directories" in the left pane, add a new path after $(IncludePath) in the property grid, delimited by a semicolon for "Include Directories".
  5. Click the drop-down for "Include Directories", choose "edit". In the dialog box that comes up, use the arrows in the upper pane to reorganize the directories.

2.4.1.27 Renaming a C++ Windows Form, which is checked into source control from the IDE, reports error

Renaming a C++ Windows Form, which is checked into source control from the IDE, reports error.

To resolve this issue:

  1. Check out the Windows Form from source control.
  2. Rename it, and check it in.

2.4.1.28 DTE.Commands.AddCommandBar() does not persist command bars

Adding command bars through DTE.Commands.AddCommandBar() will not persist the command bar.  Therefore, after Visual Studio is restarted, the command bar will not be available.

To resolve this issue:

If you want to add a command bar to a top-level menu (for example, Toolbars and Context Menus), use DTE.CommandBars.Add() as an alternative workaround.  However, if you want to add a command bar in a menu, you have to:

  1. Ensure that the add-in is loaded on startup.  You can configure this setting in Tools->Add In Manager.
  2. After the add-in is loaded, you can retrieve the DTE command bar instance and add the controls by using the Add() method that is located on the Controls property of DTE.CommandBar.

2.4.1.29 Changing two property values causes error

Bring up the property pages, change two properties on the property page, and then click "OK". This causes the "Object Reference not set to instance" error to appear.

To resolve this issue:

First click "Apply" to persist the settings, and then click "OK" to dismiss the dialog box.

2.4.1.30 Microsoft.Cpp.x64.user property sheets missing in Property Manager after x64 platform is added to a Visual C++ project

In the Configuration Manager, add a new project and solution platform x64 by copying settings from Win32. When you Expand Debug | x64 or Release | x64 nodes in Property Manager and inspect child property sheets, the corresponding x64 property sheets are not available.

To resolve this issue:

  1. Save the solution.
  2. Reopen the solution.
  3. The expected property sheets should appear.

2.4.1.31 Quoted command line converted incorrectly in custom rule file

If your custom build rule had this command line: "%systemroot%\system32\cmd.exe" /k echo >"$(IntDir)\sample.txt", the conversion incorrectly escapes the quotation marks. This causes the command line after conversion to resemble this: "%systemroot%\system32\cmd.exe" /k echo >"$(IntDir)\sample.txt.

To resolve this issue:

  1. Open the corresponding .targets file for your rule in a text editor.
  2. Fix the <Commandline> attribute to reflect the missed quotation marks.
  3. Save.

2.4.1.32 Clean Solution does not work for Configuration Type: Makefile (2010 RC)

Doing "Clean Solution" on nmake solution reports the following error:

1>------ Clean started: Project: makefiletest, Configuration: Debug Win32 ------

1>  'nmake' is not recognized as an internal or external command,

1>  operable program or batch file.

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.MakeFile.Targets(33,5): error MSB3073: The command "nmake /?" exited with code 9009.

============== Clean: 0 succeeded, 1 failed, 0 skipped ==========

To resolve this issue:

  1. Open Visual Studio Command Prompt window. >
  2. Use devenv /useenv to open the IDE.
  3. Now "Clean Solution" should work.

Or:

Pass a batch file to the clean command.  In the batch file, set up PATH to the nmake tool as well as the other build environment.

2.4.1.33 Using ">File.OpenFile" or ">of" does not autocomplete the file name for certain file name extensions

If you use the Command Window or the "Go To Find Combo" in the Standard toolbar to open files by using ">File.OpenFile <filename>" or ">of <filename>", autocomplete results for certain file name extensions will not appear.  The two known affected file name extensions are .xaml files and .svc files.

To resolve this issue:

Option 1: Type the full name of the file (for example, ">of MainWindow.xaml").

Option 2: Open any file in the project that contains the file you want to open .  If any file in that project exists in the Tab Well, autocomplete will work for all files in that project.

2.4.1.34 Exception when creating a static library project by using "New Project From Existing Code"

Performing the following steps reports the following error:  "Error message: Object reference not set to an instance of an object, which is NullReferenceException"

  1. Create a folder that has some .cpp files.
  2. In Visual Studio, run File->New->Project From Existing Code from that folder, select C++, browse to the folder, name the project, click Next.
  3. Select Static Library project type and click Finish.

To resolve this issue:

  1. Select another project type instead of Static Library project type and click Finish.>
  2. After the project is created, change the project type by changing the project properties.

2.4.1.35 Migrating property sheets from Visual Studio 2008 to Visual Studio 2010 fails to upgrade OutputFile property

If you run migration and you have property sheets that change properties for both the Linker and the Librarian tools, after conversion only the properties in the Linker or only the properties in the Librarian will be converted. Properties in the other one of the tools will still have their default values.

To resolve this issue:

  1. Open the property sheet in Visual Studio 2010.>
  2. Modify the Librarian or Linker properties manually.

2.4.1.36 IntelliSense Error (#error directive: Please use the /MD switch for _AFXDLL builds c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\afxver_.h) shown on default auto generated MFC projects

Create an MFC application by using the default template and open one of the generated .cpp files. Open the errorlist window and notice that IntelliSense errors occur in the autogenerated files. The following IntelliSense error is reported:

#error directive: Please use the /MD switch for _AFXDLL builds c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\afxver_.h

To resolve this issue:

  1. Open the project in Visual Studio 2010.>
  2. Right-click the Project.
  3. Go to Config Properties->C/C++-> Code Gen ->. Double-click "Runtime Library" and set to "Multi-threaded Debug DLL (/MDd)" . If this value already appears to be set, make sure it is by selecting it again (it should then appear as bold).
  4. Click OK.

2.4.2 Code Editor

2.4.2.1 IntelliSense is not enabled for users who are upgrading from an earlier version of Visual Studio and who use ReSharper

Customers who use JetBrains ReSharper with Visual Studio 2008 or earlier may not get IntelliSense after they upgrade to Visual Studio 2010 and migrate their settings.  When ReSharper is used, it disables the default Visual Studio IntelliSense and replaces it with ReSharper IntelliSense, and the user's .vssettings file records that Visual Studio IntelliSense is not enabled.  When Visual Studio 2010 is installed, it automatically migrates the user's settings file from the earlier version of Visual Studio; this includes the setting that disables IntelliSense.

To resolve this issue:

There are two ways to fix this issue:

  1. Install a build of ReSharper that is compatible with Visual Studio 2010.>
  2. Re-enable IntelliSense in Visual Studio 2010. To do this, go to Tools->Options->Text Editor->[language]->General and select "Auto list members".  C# users might also have to go to Tools->Options->Text Editor->C#->IntelliSense and reset those options.

2.4.2.2 User Keywords color settings imported from Visual Studio 2008 do not get reflected in the Visual C++ editor in Visual Studio 2010

User Keywords color settings imported from Visual Studio 2008 do not get reflected in the Visual C++ editor in Visual Studio 2010.

To resolve this issue:

There is no workaround.

2.4.2.3 IntelliSense live error reporting and Quick Info tooltips do not work during debugging in the Visual C++ editor

The IntelliSense live error reporting (wavy underlines) and Quick Info tooltips (information shown when you move the pointer over code)  are not available for C++ during debugging.  The tooltip UI gets used by expression evaluator during debugging.

To resolve this issue:

There is no workaround. Currently live error reporting and tooltip information are not supported for C++ when debugging.

2.4.2.4 Full IntelliSense support is not available for C++/CLI

A subset of IntelliSense is unavailable for C++/CLI code in Visual Studio 2010. This includes:

However, all code browsing features (ClassView, GotoDef, Find All References, Navigate To, and so on) are available for C++/CLI.

To resolve this issue:

There is no workaround.

2.4.2.5 Some real-time anti-virus software may slow the performance of the Visual C++ IDE

Real-time anti-virus software may interfere with the Disk I/O that the Visual C++ IDE requires.  This I/O can be for compilation or linking, or for updating the database that is used for IDE functionality.  The typical observed performance slowdown is 15-30%.

To resolve this issue:

Exclude your source directories from anti-virus scanning.  This ensures that the anti-virus software does not lock the files that are being modified by the IDE.

Alternatively, you can selectively exclude the file type SDF from virus scanning.  In Visual Studio 2010, the Visual C++ IDE uses a SQL Server Compact database to provide IDE code-browsing functionality.  The database file created has the file name extension .sdf.  Excluding such files from scanning ensures that these files are not locked by the anti-virus software when the IDE wants to access them.

2.4.3 Languages

There are no known issues.

2.4.4 Visual Studio Tools for Office

2.4.4.1 Opening a Visual Studio 2010 Beta 2 VSTO project in Visual Stuido 2010 release version does not build

Office projects that were created in Visual Studio 2010 Beta 2 and target the .NET Framework 4 will not compile in Visual Studio 2010 release version.

To resolve this issue:

To compile the project in Visual Studio 2010 release version, you must regenerate the code-behind files. There are two ways to do this.

Option 1:

  1. Make sure that the project is not open in Visual Studio 2010.
  2. Delete all of the *.Designer.cs, or *.Designer.vb files from the project. For example, in a Visual C# add-in project, delete ThisAddIn.Designer.cs files.
  3. Open the project in Visual Studio 2010. When you open the project, Visual Studio automatically regenerates the deleted files by using code that compiles.

Option 2:

  1. Open the project in Visual Studio 2010.
  2. Change the .NET Framework target of the project to the .NET Framework 3.5.
  3. Change the .NET Framework target back to the .NET Framework 4 or the .NET Framework 4 Client Profile. After you retarget the project, Visual Studio automatically regenerates the deleted files by using code that compiles.

2.4.5 SharePoint Development

2.4.5.1 Deploying BDC models to SharePoint Foundation 2010 causes an error

If you attempt to deploy a BDC model created in Visual Studio 2010 to SharePoint Foundation 2010, you get the following error message:

Error 1 Failed to load receiver assembly "Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" for feature "SharePointProject4_Feature2" (ID: 90146a35-91c1-4d4d-ac01-8cd24614b540).: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
&nbs   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

To resolve this issue:

Do one of the following actions:

2.4.5.2 Team Build Support for SharePoint Projects

Team build of SharePoint projects is not supported by out-of-box functionality of TFS/Team Build because of the dependency on SharePoint and custom build targets and tasks.

To resolve this issue:

MSDN article here: http://go.microsoft.com/fwlink/?LinkID=165499 provides step-by-step instructions for customers to manually enable the building and packaging of SharePoint Projects on a TFS/Team Build computer.

2.4.5.3 Error occurs when a SharePoint site is created by using a second site definition

If you have a SharePoint solution that contains two site definitions, and you create a site by using the first site definition, you get the following error if you attempt to create a site based on the second site definition:

"Error

The template you have chosen is invalid or cannot be found.

FAILED hr detected (hr = 0x81071e44)"

To resolve this issue:

Either close Visual Studio and then restart it, or end the vssphost.exe process by using Task Manager.

2.4.5.4 Inline debugging of Application Page and Visual Web Part items does not work

Execution does not stop at breakpoints that are set in the XML markup of an application page or visual Web Part.

To resolve this issue:

  1. On the Debug menu, click Options and Settings.>
  2. In the Options dialog box, click General, and then clear "Require source files to exactly match the original version".

2.4.5.5 URL picker is not enabled for some Sharepoint controls

You cannot invoke the URL picker from properties of the CSSLink control and the DateTimeControl.

To resolve this issue:

There is no workaround.

2.4.5.6 Assembly is not added to the \bin\ folder after a customized server control is added

If you add a customized server control to the project, the assembly that contains the control is not automatically added to the \bin\ directory when you compile the project. As a result, the assembly is not deployed to the SharePoint server when you run the project.

To resolve this issue:

On the Advanced page of the Package Designer, add the custom assembly.

2.4.5.7 SharePoint 2010 is required to create SharePoint projects

To create a SharePoint project, you must have SharePoint 2010 installed locally on the system.

To resolve this issue:

Install SharePoint Foundation 2010 or SharePoint Server 2010 on the same system that has Visual Studio 2010.

2.4.5.8 New language features are not supported in SharePoint projects

In Visual Studio 2010, several new Visual C# and Visual Basic language features are not available in SharePoint projects.

To resolve this issue:

There is no workaround.

2.4.5.9 Breakpoints on the Workflow Designer are not hit in SharePoint projects

Breakpoints set on the Workflow Designer do not break correctly in SharePoint projects.

To resolve this issue:

Set breakpoints in the workflow code file, either workflow.cs or workflow.vb. Breakpoints in the code file will break correctly.

2.4.5.10 Debugger displays incorrect workflow in the Designer, and/or workflow build errors are not reported

On the second deployment of a SharePoint workflow, a older version of the workflow may be displayed in the Workflow Designer during debugging.  In addition, not all build errors are displayed at all times. This is only a display issue with the Workflow Designer; the correct workflow is run in SharePoint.

To resolve this issue:

Change the signature of the assembly that is being stored in the Global Assembly Cache (GAC) on subsequent deployments. The easiest way to do this is to change the assembly version. To avoid this problem, modify the assembly.cs or assembly.vb file to auto-increment the assembly version number on every build.

2.4.6 Web Development

2.4.6.1 URL routing does not work with virtual paths that contain periods when you use the Visual Studio Development Server (Cassini) in file-system Web sites

If you create a file-system Web site in Visual Studio 2010 and the Web site is in a folder that contains a period (.) in the folder name, URL routing will not work reliably. An HTTP 404 error is returned from some virtual paths. This occurs because Visual Studio 2010 runs the Visual Studio Development Server (Cassini) by using an incorrect path for the root virtual directory.

For example, if a file-system Web site is created in a folder that has the name "somedot.path", a request to the following URL will fail with an HTTP 404 error:

http://localhost:1234/somedot.path/example

However, a request to the following URL will succeed:

http://lochttp://localhost:1234/somedot.path/example.aspx

To resolve this issue:

You can use one of the following workarounds for this issue:

2.4.6.2 Unit Test Project Does Not Contain Reference To ASP.NET MVC 2 Project

If the Solution Explorer window is hidden in Visual Studio, when you create an ASP.NET MVC 2 Web application project and you select the option Yes, create a unit test project in the Create Unit Test Project dialog box, the unit test project is created but does not have a reference to the associated ASP.NET MVC 2 project. When you build the solution, Visual Studio will display compilation errors and the unit tests will not run.

To resolve this issue:

There are two workarounds. The first is to make sure that the Solution Explorer window is displayed when you create an ASP.NET MVC 2 Web application project. If you prefer to keep Solution Explorer hidden, the second workaround is to manually add a project reference from the unit test project to the ASP.NET MVC 2 project.

2.4.6.3 Some Features are Unavailable in the Web Development (Code Optimized) Profile

The HTML Designer is not available in the Web Development (Code Optimized) Profile.  Features that require the Designer, for example, the Style Builder, are not available in this profile.

To resolve this issue:

The HTML Designer can be enabled by using a profile other than the Web Development (Code Optimized) Profile. To change the profile being used, on the Tools menu, select Import and Export Settings.  Reset the settings and select a different profile.

2.4.6.4 Some Visual Studio 2010 Web Deployment Features will not work if Visual Studio 2010 is installed on Windows Vista RTM instead of Windows Vista SP1

If the new Web Deployment features in Visual Studio 2010 are used together with any of the following features (which integrate with MSDeploy)

then Windows Vista users must have Service Pack 1 installed.

To resolve this issue:

MSDeploy requires features in Windows Vista SP1. Therefore, trying to run Web Deployment features on Windows Vista RTM fails.  Windows Vista must be upgraded to Service Pack 1 in order to use the Web Deployment features in Visual Studio 2010.  You can also use Windows XP, Windows 2003, Windows 2008 R2, or Windows 7 to install Visual Studio 2010 and use the Web Deployment features. (However, we recommend that you always use the most up-to-date operating system Service Packs so that all the required dependencies are in place).

2.4.6.5 ASP.NET Development Server requires IPv4 to be installed

The ASP.NET Development Server (aka Cassini) requires IPv4 to be installed on the development computer.  IPv4 does not, however, have to be enabled.

To resolve this issue:

If security policy requires IPv6 to be used, IPv4 can be installed but not enabled on the development computer.  Alternatively, IIS can be used for Web site development.

2.4.6.6 Upgrading an ASP.NET 3.5 Web site that has a 3.5 Chart control to ASP.NET 4 requires changes to web.config and register directive

Updgrading an ASP.NET 3.5 Web site that has a 3.5 Chart control to ASP.NET 4 will cause the following error on build:

Error 1 The type 'System.Web.UI.DataVisualization.Charting.Chart' exists in both 'c:\Windows\assembly\GAC_MSIL\System.Web.DataVisualization\3.5.0.0__31bf3856ad364e35\System.Web.DataVisualization.dll' and 'c:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Web.DataVisualization.dll' C:\Websites\Vs2008Sp1_Website_35_Cs_WithChart\Default.aspx 15

To resolve this issue:

References that still point to the 3.5 Chart control in web.config after upgrade must be updated to reference version 4.

<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID">lt;controls>

<add tagPrefix="asp" namespace="System.Web.UI.DataVisualization.Charting" assembly="System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</controls>

</pages>

<httpHandlers>

<add path="ChartImg.axd" verb="GET,HEAD" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>

</httpHandlers>

......

<system.webServer>

<validation validateIntegratedModeConfiguration="false"/>

<handlers>

<remove name="ChartImageHandler"/>

<add name="ChartImageHandler" preCondition="integratedMode" verb="GET,HEAD" path="ChartImg.axd" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</handlers>

</system.webServer>

......

Register directive in the Web forms page must be removed or updated to reference version 4.

<%@ Register assembly="System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" namespace="System.Web.UI.DataVisualization.Charting" tagprefix="asp" %>

The existing System.Web.DataVisualization assembly in the bin folder may have to be deleted because this assembly is part of the .NET Framework 4.

2.4.7 Windows Communication Foundation (WCF) Tools

There are no known issues.

2.4.8 Windows Presentation Foundation (WPF) Tools

2.4.8.1 WPF & Silverlight Designer Team Blog

The WPF & Silverlight Designer Team (Cider Team) has just started a new team blog at: http://blogs.msdn.com/wpfsldesigner/default.aspx

This initial content will focus on the Designer toolset, walkthroughs that use the Designer, and FAQ and posts for control authors. Additionally, you can leave feedback for the Cider Team on the blog.

You can find these README items on the blog at: http://go.microsoft.com/?linkid=9723703

To resolve this issue:

Not applicable.

2.4.8.2 User code exceptions may affect designer and Visual Studio

Any user code that throws an exception at design-time can cause unhandled exceptions in the designer and may even cause Visual Studio to crash.  To protect against this, prevent your code from executing at design time by wrapping it with DesignerProperties.GetIsInDesignMode checks.  Common examples of methods that will be executed at design-time are the UserControl.Loaded event handler, binding converters, and WCF async event handlers.

To resolve this issue:

Refer to the following articles:

2.4.8.3 Assemblies downloaded from the Web fail to load

In Visual Studio 2010, assemblies that have been downloaded from the Web may not load correctly.  This is because these assemblies have been given the "Mark of the Web" and thus are not fully trusted.  Using these assemblies as-is may cause errors when you build an application, reference these assemblies in XAML, or try to consume one of these assemblies through the Choose Items dialog box.  In these cases, the error will generally indicate that this assembly may have been downloaded from the Web.

To resolve this issue:

If you fully trust these assemblies, you can work around this issue by following the instructions here:

http://go.microsoft.com/fwlink/?LinkId=179545

2.4.8.4 Resources from external Silverlight 3 assemblies fail to resolve at design-time

Resources from external Silverlight assemblies (that is, the projects that build these assemblies are not part of your solution) will fail to be found by the designer.

To resolve this issue:

For any Silverlight ResourceDictionary that is contained in an assembly that will be consumed as an assembly reference, you must include the following in the ResourceDictionary definition:

    x:Class="ResourceDictionary"

As a more detailed example, your ResourceDictionary has to resemble this:

<ResourceDictionary

    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">

</ResourceDictionary>

2.4.8.5 Upgrading version 3.5 projects to version 4 may cause build errors

For this release of Visual Studio, some types were moved to the System.Xaml assembly.  As a result, retargeting your project from version 3.5 to version 4 may cause errors that indicate:

This type has been forwarded to assembly 'System.Xaml'.

To resolve this issue:

Manually add this assembly to your project and rebuild.

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 If Microsoft Test Manager is not shut down cleanly, the HTTP Proxy settings may be incorrect and prevent Web sites from loading

If Microsoft Test Manager (MTM.exe) is not shut down cleanly (that is, crash, hard reset, power cycle), and the "ASP.NET Client Proxy for IntelliTrace and Test Impact" diagnostic data adapter was enabled in test settings, the Internet proxy settings will not be reverted on the client machine.  This can hamper Internet traffic; this includes Web site rendering.

To resolve this issue:

2.4.11.2 Debugger start fails if the IntelliTrace recordings directory is Read-Only

By default, IntelliTrace files are located in the "%ProgramData%\Microsoft Visual Studio\10.0\TraceDebugging\" directory.  If this directory is made read-only, or the directory is changed to a read-only location, an uncaught exception gets raised to the user.  "Error while trying to run project: Uncaught exception thrown by method called through Reflection."

To resolve this issue:

2.4.11.3 Error message while debugging an application that uses Microsoft native parallel library

When debugging an application that uses the Visual C++ task-based parallel libraries that are part of the CRT version 10.0, you may encounter an error message in the Parallel Tasks (and Parallel Stacks) window.

                "This view is supported only for programs that target Visual C++ 10 or later. Try loading symbols. Symbol Settings..."

Loading symbols, as the error message suggests, should resolve the issue. If it does not, it is because your debugging session is using symbols downloaded from the Microsoft public symbol server instead of the ones installed on your computer by Visual Studio.

To resolve this issue:

Before you debug your application, follow these steps:

  1. Go to Tools -> Options -> Debugging -> Symbols.
  2. Check "Microsoft Symbol Server" entry under "Symbol file(.pdb) locations:" If you are already using symbol cache, delete the folder that contains downloaded CRT symbols.
  3. Add an explicit symbol path entry (and check) under "Symbol file(.pdb) locations:" pointing to "<windir>\symbols\dll". Note: < windir > is the Windows installation folder; for example: 'C:\Windows'

2.4.11.4 Importing a pinned DataTip crashes Visual Studio

In design mode, importing a DataTip that already exists and is pinned to the source code causes Visual Studio to crash.

To resolve this issue:

There are two workarounds for this issue:

  1. Import DataTips in debug mode instead of design mode.>Clear Clear the pinned DataTip before you import a DataTips file that contains a duplicate copy of an existing pinned DataTip.

2.4.12 Architecture Tools

There are no known issues.

2.4.13 Testing Tools

2.4.13.1 Because of read-only file issues, upgrading a Visual Studio 2008 solution that has a test project, test run configuration, and .vsmdi fails

Upgrading a solution from Visual Studio 2008 to Visual Studio 2010 fails when the .testrunconfig or .vsmdi files are read-only. During upgrade, a message is displayed and says that the upgrade failed.

To resolve this issue:

Before you open the solution, make sure that the files are not read-only.  If the files are checked into source control and are read-only, check out the files before you open the solution.

2.4.13.2 Running automated test cases on a network-isolated virtual environment takes more time than expected

When you run automated test cases on a network-isolated virtual environment, you might observe that the test agent remains in the "Running Test" state for a few minutes after execution of the test case is complete.  This happens only if:

  1. You run the test cases on a network-isolated environment, where the virtual machines are connected to a different domain than the machine on which test controller is installed. >In the network-isolated environment, there is at least one virtual machine being used only for data collection (that is, there are no tests running on the machine).
  2. You are not using local shadow accounts for the agent-controller communication and have configured the lab service account in the team project collection.

To resolve this issue:

  1. Run test controller under a domain account that is different from the lab service account. Let us say that the domain account is mydomain\myaccount. >In the network-isolated environment, shadow this domain account on the lab computer(s) that are executing the test cases. You can identify those computers in your environment by matching the role of each computer with the execution role in your test settings. For example: if the execution role in your test settings is "Database Server", then you have to shadow it only on the computers that have role = "Database Server" and you do not have to shadow it on the other computers in the environment. (Shadowing the domain account means that you should create a local computer account that has the name "myaccount" and the same password as the one for mydomain\myaccount.)
  2. Restart the test controller and now run the test cases.

Note: If after some days the password for the test controller account changes, you must update the password on the computers where you have shadowed it.

2.4.13.3 Coded UI Test projects created in Beta 2 have to be upgraded to the release version. In addition, there have been significant changes in the API. All projects created with Visual Studio 2010 Beta 2 must be upgraded to the release version

The list of changes are as follows:

  1. UserControls.cs file has been removed. All specialized classes (HtmlButton, WinEdit, WpfCheckbox etc) are now part of the product.
  2. 'Internet Explorer Server' control used to be part of the UI Control hierarchy for Html Controls. This has been removed to enable better support for extensibility.
  3. For searching a Browser Window, exact name match is now used.
  4. The names of properties (e.g: DisplayText of a HtmlButton) previously used to be in a separate class hierarchy (for example: HtmlProperties.Button.DisplayText). This has now been modified to be part of the definition of each specialized class. Therefore, HtmlButton.PropertyNames.DisplayText will now give the name of the DisplayText property of HtmlButton.
  5. Classes that did not have any additional property on them will now be treated as a Custom class. For example: HtmlForm will now be treated as an HtmlCustom and its TagName property will be set to 'Form'. Windows Forms controls that do not have additional properties will be treated as a WinControl. WPF controls that do not have additional properties will be treated as a WPFControl.

To resolve this issue:

  1. Download and install the UI Test Upgrade tool from http://go.microsoft.com/fwlink/?LinkId=184024
  2. Run the Visual Studio Command Prompt window.
  3. Run the following script:

UITestUpgrade.exe <name of folder(s) to upgrade>

2.4.13.4 Some accented characters cannot be typed while a test is being executed in Test Manager or while recording a test in Coded UI Test

When the Test Recorder is executing (or while recording a test in Coded UI Test), no accented characters must be typed as a combination of an accent and a "base" character. The issue is that the Test Recorder interprets the accent as a "dead key" and discards it.

To resolve this issue:

Finish recording the Test and then manually modify the generated code by adding the required accented characters.

A QFE may be available - please contact Customer Support Service.

2.4.14 Lab Management Tools

There are no known issues.

2.4.15 Team Explorer

There are no known issues.

3. Related Links

 

© 2010 Microsoft Corporation. All rights reserved.

Terms of Use | Trademarks | Privacy Statement