For the most current version of the Readme, click here.
Visual Studio 2010 and/or the .NET Framework 4 Setup fails with a 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 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.
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.
Rerun Visual Studio Setup
Related KB Article
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 you install Visual Studio 2010. 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.
Network issues occasionally cause corrupted files when they are downloaded from a network and then installed, or when the files are installed over a network. This issue will manifest itself by writing 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 full Express CD and install the product locally.
When you install Visual Studio on a Netbook, the navigation buttons at the bottom of the dialog box may not appear.
To resolve this issue:
Check the display resolution to ensure that you have allowed for the minimum required resolution:
To do this on Windows XP:
To do this on Windows Vista or Windows 7:
When you install Visual Studio 2010, if you unplug your USB drive, your installation might either prompt for source or fail to install because of missing temporary files.
To resolve this issue:
Either unplug all USB Drives before you install Visual Studio, or do not unplug these drives during Setup because some temporary files may get copied and used on the drive that has the largest amount of free space.
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.
Clicking the "Install Documentation" button starts the Help Library Manager, which is the application that lets you install local help. Help Library Manager first prompts you to set 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.
If Setup determines that SQL Server 2008 Express SP1 cannot be installed on the computer, Visual Studio 2010 will remove SQL Server 2008 Express from the list of components available to install. In this case, the installation of SQL Server 2008 Express SP1 is blocked by the existing installation of SQL Server 2005 Express. To install SQL Server 2008 Express SP1, uninstall SQL Server 2005 Express and then rerun Visual Studio 2010 Setup, or install SQL Server 2008 Express SP1 as a separate installation.
SQL Server 2005 Express cannot be upgraded to SQL Server 2008 Express SP1 in the following situations:
To resolve this issue:
Workaround 1 - Uninstall existing SQL Server 2005 Express Editions and then rerun Visual Studio Setup.
Workaround 2 - Install SQL Server 2008 Express SP1 separately.
If a version of the Silverlight 3 SDK is already installed, additional language versions of it will not be installed by Visual Studio 2010.
To resolve this issue:
You can download additional language versions of the Silverlight 3 SDK from http://go.microsoft.com/fwlink/?LinkID=157102 and install them side-by-side with other Silverlight SDK versions.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
Visual Studio 2010 may install important system updates.
To resolve this issue:
We recommend that you keep these updates on your system after you remove Visual Studio:
This section applies to Visual Studio 2010. All pre-release versions must be removed in the correct order BEFORE you install the official release version. For instructions about how to uninstall earlier versions, see:
All pre-release versions must be removed in the correct order BEFORE the official release version is installed. We recommend that you uninstall the main product first (for example, Visual Basic 2010 Express), which removes the majority of the components. Then, uninstall other supporting products that may also have been installed.
To resolve this issue:
For complete steps, see the uninstall documentation on MSDN.
Setup does not remove local help content when you uninstall Visual Studio. The default location for the local content directory changed between Beta 2 and this release.
To resolve this issue:
If you have already uninstalled Visual Studio, you can manually delete the files in the local help content directory. If you did not reuse the Beta 2 local help content directory you must manually delete the Beta 2 content directory to remove it from your computer.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
After you install Visual Studio, you can add components that were not installed by default.
To resolve this issue:
To install optional components on Windows XP or earlier versions of Windows
To install optional components on Windows 7 or Windows Vista
If Visual Studio becomes unstable, you can 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.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
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:
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\General]
"UIAOverride"=dword:00000001
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:
When you reset your user data and import a Visual Studio 2008 settings file, the contents in the Options dialog box under Projects and Solutions displays incorrect values.
To resolve this issue:
If necessary, remove the extra "1" at the end.
Help Library Manager (HLM) uses the BITS service to download content. If HLM is started 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 you download content, start HLM under the user account that is currently logged on.
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:
You can add 127.0.0.1 to the I.E. trusted sites. Alternatively, for the search button issue, you can press ENTER to perform the search.
When Help Library Manager (HLM) is running on Windows XP, if you attempt to set the local content store 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.
When you start Help Library Manager for the first time, you are prompted for the location where local content will be stored. 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.
A window titled "Help Library Agent Invisible Window" can become visible. If you close the window, the Help Library Agent will stop responding.
To resolve this issue:
Use Task Manager to end the agent process. It will restart itself when you restart Help by using the shortcut, Help menu, or F1.
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, start Visual Studio 2010 by using "devenv" and not "devenv /useenv".
"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, in the IDE, click "View -> Property Manager".
Managed Incremental Build for Visual C++ managed projects is not supported in Visual Studio 2010.
To resolve this issue:
There is no workaround.
If you bring up the property pages and change two properties on the property page, and then click "OK", an "Object Reference not set to instance" error appears.
To resolve this issue:
If you encounter this issue, first click "Apply" to persist the settings and then click "OK" to dismiss the dialog box.
When a new x64 platform is created from a Win32 platform for C++ projects, TargetEnvironment property is not correctly copied. This may cause link errors.
To resolve this issue:
Doing "Clean Solution" on an 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:
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.
Performing the following steps reports this error: "Error message: Object reference not set to an instance of an object, which is NullReferenceException"
To resolve this issue:
If you run migration and you have property sheets that change properties for both Linker tools and Librarian tools, after conversion, only the properties in the Linker or only the properties in the Librarian will be converted. Properties in one of the tools will remain to be their default values.
To resolve this issue:
There are no known issues.
There are no known issues.
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 will need to look like this:
<ResourceDictionary
x:Class="ResourceDictionary"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" P> xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
</ResourceDictionary>
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 therefore are not fully trusted. Using these assemblies as-is may cause errors when you build an application, reference these assemblies in XAML, or attempt to consume one of these assemblies by using 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 may work around this issue by following the instructions here:
http://go.microsoft.com/fwlink/?LinkId=179545
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:
The HTML Designer is not available in the Web Development (Code Optimized) Profile. Therefore, features that require the HTML 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, on the Tools menu, click Import and Export Settings. Reset the settings and then select a different profile.
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 SP1 installed.
To resolve this issue:
Upgrade to Windows Vista SP1. The Web Deployment features in Visual Studio 2010 also work on Windows XP, Windows Server 2003, Windows Server 2008 R2, or Windows 7. (Note: We recommend that you always use the most up-to-date operating system Service Pack so that all the required dependencies are in place.)
The ASP.NET Development Server requires IPv4 to be installed on the development computer. However, IPv4 does not have to be enabled.
To resolve this issue:
If security policy requires IPv6 to be used, install IPv4 on the development computer but do not enable it. Alternatively, IIS can be used for Web site development.
When an ASP.NET 3.5 Web site that has a 3.5 Chart control is upgraded to ASP.NET 4 and built, the following error occurs:
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:
After the upgrade, in web.config, update references that still point to the 3.5 Chart control to point to version 4.
<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID">
<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" %>
You may have to delete the existing System.Web.DataVisualization assembly in the \bin\ folder because the assembly is part of the .NET Framework 4.
For details about what's new in ASP.NET MVC 2, see http://go.microsoft.com/fwlink/?LinkID=185038. This includes a list of breaking changes and known issues.
© 2010 Microsoft Corporation. All rights reserved.