Notes

1. Performance has not been tuned for minimum system configuration. Increasing your computer's RAM will improve its performance, especially when running multiple applications, working with large projects, or doing enterprise-level development.
   
   For Visual Studio Tools for Office features, 256 megabytes of RAM is required. This requirement only applies to Microsoft Visual Studio 2005 Team Edition for Software Architects, Microsoft Visual Studio 2005 Team Edition for Software Developers, Microsoft Visual Studio 2005 Team Edition for Software Testers, and Microsoft Visual Studio 2005 Team Suite.
    
2. When you start the Visual Studio 2005 installer, the default installation location is your system drive, which is the drive that boots your system. However, you can install the application on any drive. Regardless of the application's location, the installation process installs some files on your system drive. Consequently, ensure that the above amount of space is available on your system drive regardless of the application's location, and ensure that additional space, as listed above, is available on the drive on which you install the application.

Visual Studio 2005 does not support the Intel Itanium (IA64) processor.

To resolve this issue

If you need to develop Itanium applications, install Visual Studio on another computer and use the cross compilers to target the Itanium platform.

SQL Express component setup will fail if any of the following pre-released SQL Express components are left on the computer:

"Microsoft SQL Server 2005 Express Edition"
"Microsoft SQL Server 2005 Tools Express Edition"
"Microsoft SQL Native Client"

In most cases, setup only displays a list of Beta components detected on the targeted computer. However, SQL Express components will always appear in this list if any other Beta components are detected. In other words, these SQL Express components could appear in the list even after the user uninstalls them.

To resolve this issue

Ensure the matching .NET Framework Beta is on the computer before performing the following steps:
1) Remove "Microsoft SQL Server 2005 Express Edition"
2) Remove "Microsoft SQL Server 2005 Tools Express Edition"
3) Remove "Microsoft SQL Native Client"
You may ignore the Beta warning message about these components if they were uninstalled previously.

When installing Visual Studio 2005 on a Virtual PC, setup fails because it cannot access certain files.
This happens when the drive is mounted using the CD Drive mount software provided with Virtual PC or your Visual Studio 2005 media is a DVD because the mounting software can only support 2.2 Gigabytes of data.

To resolve this issue

You can use a third-party DVD Drive mounting software. Alternatively, you can copy the contents of the Visual Studio 2005 DVD to your computer's hard drive, share the folder with your Virtual PC, and then direct Visual Studio 2005 installation setup to the folder.

On a system with Office 2003 SP2 or later, installing Visio for Enterprise Architects reverts three files shared with Office to SP1 versions. This also occurs with certain downloaded and installed updates to Office 2003 SP1. The affected files are MSSP3EN.LEX, MSSP3ENA.LEX, and FPEXT.MSG. No known serious functionality issues result from changes to these files.

To resolve this issue

From an Office application, run the "Detect and Repair" command from the Help menu. This restores the affected files to their correct versions.

Unless you are logged in as an administrator, using the runas command to install Visual Studio 2005 is not supported and will fail. Running Visual Studio 2005 after it is installed is supported for non-administrators.

To resolve this issue

Log in as an administrator to install Visual Studio 2005.

The media that Visual Studio 2005 shipped on may be bad, preventing a successful installation.

To resolve this issue

Visual Studio 2005 setup may be run from a network share as an alternative to running setup from CDs or DVDs. The following procedure illustrates how to prepare Visual Studio 2005 for installation from a network share. The procedure refers to the Visual Studio 2005 CDs, but the steps are the same for DVDs.

1) Create a folder (for example, VS2005) on the server.
2) Create two subfolders, named VS, and MSDN within the top-level folder. For example:
    VS2005\VS
    VS2005\MSDN.

3) Copy the contents of the Visual Studio 2005 CDs into the VS2005\VS folder. Select Yes if prompted to overwrite any existing files.
4) Copy the contents from all the CDs labeled MSDN Library for Visual Studio 2005 to the subfolder named MSDN. Select Yes if prompted to overwrite any existing files.
5) Open Setup.ini in the VS subfolder using a text editor, such as Notepad.
6) In the [Documentation] section, change the line that starts with "DIR=" as follows:
    [Documentation]
    DIR=..\MSDN

7) Save your changes and close the file.
Note Completing this step prevents disk-swapping requests during setup and informs the setup program of the correct path to the MSDN Library CDs.

8) In the VS subfolder, open the Setup folder.
9) Open setup.sdb in a text editor, such as Notepad, and add the following lines to the end of the file:
    [Product Key]
    XXXXXXXXXXXXXXXXXXXXXXXXX
Note XXXXXXXXXXXXXXXXXXXXXXXXX is the 25 digit product key, entered without dashes, found on the CD packaging.

10) Save your changes and close the file.
Note Completing this step enables pre-populating the product key for the user who will install from the network share.

11) Share the VS2005 folder on the network and set the appropriate security settings. The path to Visual Studio 2005 setup from the network looks like \\[servername]\VS2005\VS\setup.exe

Note Setup will fail if any path and file name combination exceeds 260 characters. The maximum length of a path in Visual Studio is 221 characters. You should copy files to a path with less than 70 characters. If you create a network share for a network image, the UNC path to the root installation location should contain fewer than 39 characters.

Note Setup might fail if the folder names in this path include embedded spaces, for example:
\\[servername]\VS2005\MSDN\
\\[servername]\VS2005\Visual Studio\

When setup is launched from a path that is longer than 100 characters, setup fails due to a maximum path limitation in Windows 2000. Path length is not an issue on Windows XP or Windows 2003 Server.

To resolve this issue

When installing from a network, map the network path to a local drive and install from that drive. For example, if the path is \\computername\programs\test folder\development tools\external\Microsoft\Visual Studio 2005\beta release, you can map it to a network drive by doing the following:

1) From the Start menu, choose Run.
2) Type cmd and then click OK.
3) At the command prompt, type the following:
    net use * "\\computername\programs\test folder\development tools\external\Microsoft\Visual Studio 2005\beta release"

Windows maps the network drive for you. The drive letter is displayed in the console window.

When installing from a local folder, copy the contents of Visual Studio to another folder on the computer that has a total path length of less than 100 characters.

Note: If you install Visual Studio from a CD or DVD, you will not encounter any path length issues.

To completely uninstall Visual Studio, you must manually uninstall MSXML 6.0 using Add or Remove Programs. During uninstall for MSXML 6.0, the following warning may appear:

Warning 26002. The following product(s) is dependent on MSXML 6.0. If you uninstall MSXML 6.0, they will be broken. Please uninstall those product(s) first. Do you want to go ahead to uninstall MSXML 6.0 anyway?

Microsoft SQL Server 2005 Express Edition Beta 2 (SQLEXPRESS)
Microsoft SQL Server 2005 Tools Express Edition Beta 2

To resolve this issue

You must manually uninstall all of the products listed in the warning before you uninstall MSXML 6.0.

Any SQL Server products that need to be uninstalled are listed on the final page displayed after Visual Studio is uninstalled. If products other than SQL Server are listed in the warning text, those products also will need to be uninstalled before you uninstall MSXML 6.0.

On JPN MUI OS, when installing Visual Studio Team Suite to path with non-ANSI characters such as "c:\program files\? ? ? ? ? ? ? ? Microsoft Visual Studio 8", a dialog box pops up saying "can't accept non-ANSI characters".

This problem occurs on all JPN MUI OS (including Windows 2000, Windows 2003 and Windows XP series operating systems). It does not occur on JPN OS.

To resolve this issue

Use ANSI characters for the destination path.

This error, and "Could not complete the operation due to error 887600de", might be encountered while installing Visual Studio Standard on Windows 2000 with Service Pack 4. This error occurs on computers with low color depth. This error occurs on machines with low color depth.

To resolve this issue

Enable more colors:

1. Cancel Visual Studio install.
2. Right click on the desktop wallpaper.
3. Click on Properties.
4. Click the Settings tab.
5. Adjust the Color Quality to a higher setting.
6. Click OK
7. Install Visual Studio again.

Installation of Team Load Test Agent will fail if the specified controller is not running. To verify this problem, examine AgentConfigUtil.exe.log in \Program Files\Microsoft Visual Studio 8\Microsoft Visual Studio Team Suite\LoadTest directory.

To resolve this issue

Ensure that the controller is installed and the service is running, and then try the installation again.

You want to install the Microsoft Office 2003 Primary Interop Assemblies after you have finished installing Visual Studio 2005, but you do not know how to install them.

To resolve this issue

1. On the installation media, navigate to the \setup folder.
2. Open PIAInstall.htm and follow the instructions listed.

If setup needs to reboot and your antivirus application is set to clean the Temp folder on launch, necessary setup files will be deleted and setup will fail due to a program-not-found error.

To resolve this issue

Before running Visual Studio setup, reset the antivirus application to leave Temp folder contents intact on launch or reboot. Reference your Antivirus help documentation for steps on how to do this.

When reboot later is selected and the available space on the hard drive is filled beyond the amount of space needed by setup, an out-of-space error will occur after reboot.

To resolve this issue

Ensure that enough disk space will be available by rebooting before installing or opening other applications. The required disk space is displayed when you select the location to install the product.

You must uninstall SQL Server 2005 and MSDN Library before uninstalling .NET Framework 2.0 or you will encounter an error. You can install newer versions of SQL Server 2005 or MSDN Library only after removing all previous SQL Server 2005 components and MSDN library components, as listed below.

To resolve this issue

1. From the Control Panel, select Add or Remove Programs.
2. Select SQL Server 2005 components and click Remove to remove each component below.

• Remove "Microsoft SQL Server 2005 Express Edition"
  
• Remove "Microsoft SQL Server 2005 Tools Express Edition"
  
• Remove "Microsoft SQL server setup support files"
  
• Remove "Microsoft XML 6.0"
  
• Remove "Microsoft SQLXML 4.0"
  
• Remove "Microsoft SQL Native Client"
  
• Remove "Microsoft MSDN library"

3. Select the .NET Framework 2.0 and click Remove.
4. Install SQL Server 2005.
Note: If you remove the Beta .NET Framework 2.0 before removing all SQL Server 2005 components or MSDN Library, you must reinstall .NET Framework 2.0 before you can successfully perform the steps above.

When all SQL Server Express components are uninstalled, and then SQL Server Express is reinstalled via Maintenance Mode (for VSTS, you will need to install MSXML 6.0 first), the reinstallation fails. No cause is written to the VS logs.

To resolve this issue

After uninstalling SQL Server Express, reboot the computer before reinstalling it.

The issue is that VSTO 2.0 features require an updated OtkLoader instead of the version that came with Office 2003.

When VSTS is installed, the VSTO runtime (which includes the updated OtkLoader) is installed. If Office is present at installation time, OtkLoader is updated and everything will function as expected. However, if Office is not present, OtkLoader cannot be updated. Users must then install Office SP1 and run VSTOR.EXE to update OtkLoader manually.

To resolve this issue

Run VSTOR.EXE to update the version of OtkLoader.

In order to develop applications that combine MFC and .NET Windows Forms you will need to follow an additional step.

To resolve this issue

Manually install mfcmifc80.dll to the Global Assembly Cache using the gacutil.exe.

The redistributable files for Itanium are installed to the incorrect location during the Visual Studio Tools for 64-bit Setup (available only in Visual Studio Team System products).

To resolve this issue

You can find the Itanium redistributables in the Microsoft Visual Studio 2005\VC\Redist\x86 folder.

If you localize a ClickOnce or Setup Project to Russian, the Bootstrapper (setup.exe) will not display text correctly in the EULA or Error Details dialog.

To resolve this issue

The problem is that the wrong CharSet value is used. To resolve the issue please do the following:
1. Open the setup.xml file at [.NET SDK Install Dir]\Bootstrapper\Engine\ru\seup.xml
2. Go to the bottom of the file and edit the CharSet Element's value. Change it from 0 to 204
3. Save the file.
4. Rebuild / Republish your application

When installing Visual Studio 2005 on a Virtual PC, setup fails because it cannot access certain files.
This happens when the drive is mounted using the CD Drive mount software provided with Virtual PC or your Visual Studio 2005 media is a DVD because the mounting software can only support 2.2 Gigabytes of data.

To resolve this issue

You can use a third-party DVD Drive mounting software. Alternatively, you can copy the contents of the Visual Studio 2005 DVD to your computer's hard drive, share the folder with your Virtual PC, and then direct Visual Studio 2005 installation setup to the folder.

When uninstall SQL Server Express and then reinstalling SQL Server Express, you must reboot the machine after the uninstall.

To resolve this issue

Reboot machine after uninstall completes.

When SQL Server Express is removed from your machine, MSXML 6.0 is already removed.
MSXML 6.0 is a prerequisite for Visual Studio so some features may stop working after SQL Server Express is uninstalled.

To resolve this issue

Reinstall SQL Server Express or install MSXML 6.0.
Both installers are available on the media in the \wcu folder.

These 2 assemblies are installed by Visual Studio 2005 but shipped in beta 2 with no file version information.

• Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll
• Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll

When .NET Framework 2.0 beta 2 is uninstalled before VS 2005 beta 2, these assemblies are left in the GAC. When you try to use features in the Visual Studio IDE that rely upon these assemblies, you can receive package load failures. For example, if you open a C# Windows Application and right-click on a .cs file and choose View Class Diagram, you will receive a package load failure error for the Visual Studio Class Designer Package.

To resolve this issue

1. From a cmd prompt, run del %windir%\assembly\GAC_MSIL\Microsoft.VisualStudio. EnterpriseTools.ClassDesigner\ 8.0.0.0__b03f5f7f11d50a3a\ Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll
   
2. From a cmd prompt, run del %windir%\assembly\GAC_MSIL\Microsoft.VisualStudio. EnterpriseTools.SdmDesigners\ 8.0.0.0__b03f5f7f11d50a3a\ Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll
   
3. Extract the file FL_Microsoft_VisualStudio_EnterpriseTools__66768_____X86.3643236F_FC70_11D3_A536_0090278A1BB8 from the file _9160_RTL_x86_enu_WH_ED_AppDesigner.cab on the root of the VS DVD and rename it to Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll
   
4. Extract the file FL_Microsoft_VisualStudio_EnterpriseTools__92325_____X86.3643236F_FC70_11D3_A536_0090278A1BB8 from the file _15679_RTL_x86_enu_Whitehorse_Baseline.cab on the root of the VS DVD and rename it to Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll
   
5. From a cmd prompt, run %programfiles%\Microsoft Visual Studio 8\SDK\v2.0\bin\gacutil.exe /if Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll
   
6. From a cmd prompt, run %programfiles%\Microsoft Visual Studio 8\SDK\v2.0\bin\gacutil.exe /if Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll

System Management Server may cause a conflict or sequence error while running Visual Studio setup. When MDAC is being installed as part of Visual Studio 2005, it will just fail without notifying Visual Studio.

To resolve this issue

Reboot your computer and run setup again.

Microsoft SQL Express cannot install to a compressed folder.

To resolve this issue

Either uncompress the folder or install to a different location.

ngen.exe occasionally fails with REGDB_E_CLASSNOTREG or RPC_S_SERVER_UNAVAILABLE.
The failure usually happens if you issue consecutive ngen commands back to back. Retry or reboot might help as long as you wait 15 minutes or so between two ngen commands. However, reboot does not fix the general problem and you might encounter it again

To resolve this issue

Install DCOM 98 patch from here: DCOM98Patch

Installation hangs for about an hour or more at "setup is configuring the install..." and then gives the error message "invalid directory"

This problem is caused by a lack of available disk space.

To resolve this issue

Free up sufficient space on the disk drive.

When deployed thru Active Directory, the language pack version number is displayed in the Group Policy Object - Software installation table. This can be confusing when the product name states "2.0" but the version data says "1.1"

To resolve this issue

There is no known resolution.

Upgrading using a CD with the full Windows Server 2003 SP1 installation replaces the shared file mscoree.dll on the user's computer with the .NET Framework 1.1 mscoree.dll file.
As a result, applications compiled against the .NET Framework 2.0 will fail to run after the Service Pack is installed.
Note, this does not happen when Windows Server 2003 is updated with just the Service Pack.

To resolve this issue

After installing the Windows Server 2003 Service Pack, the .NET Framework needs to be repaired.
1. From the Control Panel, select Add or Remove Programs.
2. Select Microsoft .Net Framework 2.0.
3. Click Change/Remove.
4. When the dialog appears, select Repair and click Next.
5. If prompted to do so, reboot the computer.

Existing ASP.NET 1.1 applications will be disabled when the 64-bit .NET Framework 2.0 is installed on a 64-bit operating system that has IIS6 in WoW64 mode and ASP.NET 1.1 enabled. This happens because the Framework setup incorrectly maps the aspnet_filter to the 64-bit version and removes version 1.1 of the aspnet_isapi extension.

To resolve this issue

You must manually change IIS to use the 32-bit version of the aspnet_filter and reinstall the ASP.NET 1.1 ISAPI extension.

1.    Start Internet Information Services Manager (inetmgr.exe).
2.    Expand the local computer node, then click the Web Sites node.
3.    From the Action menu, select Properties.
4.    In the Web Site Properties dialog box, select the ISAPI Filters tab.
5.    In the list of filters, select the ASP.NET 2.0 filter and click Remove.
6.    Click Add and then enter the following:
        Filter Name: ASP.NET_ 1.1.4322
        Executable: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_filter.dll
7.    Click OK.
8.    Under the Local Computer node, click the Web Service Extensions node.
9.    Under Tasks, click Add a new Web Service Extension.
10.    In the New Web Service Extension dialog box, enter the following:
        Extension Name: ASP.NET v1.1.4322
        For Required files, click Add... and then enter: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
        Check Set Extension status to Allowed.

        Click OK.

When deployed thru Active Directory, the version number is displayed in the Group Policy Object - Software installation table. This can be confusing when the product name states "2.0" but the version data says "1.1".

To resolve this issue

There is no known resolution.

If a IA64 machine has v2.0 of the .NET Framework installed, the v1.1 VJ# setup will fail. Visual Studio 2003 has a prerequisite on VJ#, so this will also prevent VS2003 from installing on a IA64 machine with v2.0 of the framework installed.

To resolve this issue

There are two workarounds available.

The easiest is to first uninstall v2.0 of the framework, and then install v1.1 of VJ#.

If uninstalling v2.0 of the framework isn't possible, then the following steps can be taken....

Install v1.1 Redist
Manually extract v1.1 J#Redist MSI file
Edit the MSI file to remove 3 components (from FeatureComponents table) that are responsible for installing the given assemblies into the GAC
Run the MSI
Manually install the 3 assemblies into the GAC using 32bit (v1.1 or v2.0) gacutil.exe

Currently, installing PB after Visual Studio 2005 will duplicate platform entries in datastore. When Visual Studio is invoked later or restarted, duplicate platform entries will be eliminated based on Platform ID without respect to how the entry was added. As a result, changes made to datastore (e.g., emulator settings) before PB was installed might be lost as part of duplicate entry removal.

To resolve this issue

Change the settings of the affected platforms manually through Visual Studio.

Uninstalling PB unregisters conman2.dll and some other dlls on which Visual Studio depends. As a result, Visual Studio smart device functionality might be impaired.

To resolve this issue

Repair-installing Visual Studio fixes the problem.

For additional information concerning Crystal Reports for Visual Studio 2005, please visit us at: http://www.businessobjects.com/products/reporting/crystalreports/net/vsnet.asp