Visual Studio .NET 2002 Readme (Part 2) (316250)

SUMMARY

This article contains Part 2 of the Visual Studio .NET 2002 Readme file. For Part 1 of the Readme, see the following Microsoft Knowledge Base article:

5 Known Installation Issues

5.1 Cannot Find Original Installation Location

When you run Setup from the Change or Remove Programs feature in the Add/Remove Programs tool in Control Panel, you may receive the following error message when you add features: You receive this error message because the CD-ROM or network location from which Visual Studio .NET was installed is no longer available. To add features, insert the CD-ROM or reconnect to the network location, and then return to Setup.

5.2 "Error 1308: Source File Not Found"

You receive this error message when you install Visual Studio .NET from a shared CD-ROM drive.

To continue with Setup, insert the next CD-ROM, and then click Retry. Repeat for each CD-ROM when the error message appears.

IMPORTANT: Visual Studio .NET cannot be shared over a network by using a shared CD-ROM drive.

For additional information about how to install Visual Studio from a network share, click the article number below to view the article in the Microsoft Knowledge Base: Then, browse to the "Facilitating Setup over a Network" section.

5.3 Error Messages When You Run Setup

When you run Setup, you may receive the following error message: This behavior occurs when critical Setup files are missing. If you are installing from a network image, recopy the CD-ROMs or DVD-ROMs to make sure that all files are available.

You may also receive the following error message: This behavior occurs if an earlier release of Visual Studio .NET, such as Beta 1, is installed on the computer.

For additional information about how to uninstall the Beta 1 or PDC Technology Preview release, click the article number below to view the article in the Microsoft Knowledge Base: Then, browse to the "Preparing to Install Visual Studio .NET" section.

5.4 "Error 1711: An Error Occurred While Writing Installation Information to Disk"

You may receive this error message if you run Setup with less than 600 megabytes (MB) of free space on your system drive.

To resolve this issue, free up space on your system drive so that you have at least 600 MB available, and then run Setup again.

5.5 Error During .NET Framework Installation When a Pre-Release Version Was Previously Installed on the Computer

After you uninstall a pre-release version of Visual Studio .NET, the Mscoree.dll file may not be removed successfully from the System32 folder. During Setup, you may receive a "1935" error message because this file is present. You may also receive a "4113" error message, with the following note: To resolve this issue, follow these steps:

1. Verify that you have run all of the steps in the "Uninstalling Pre-release Versions of Visual Studio .NET" section of the following Microsoft Knowledge Base article:

   312779 INFO: Visual Studio .NET Readme (Part 1)

2. If the issue persists, click Start, and then click Run.
3. Type %windir%\system32, and then click OK.
4. Delete the Mscoree.dll file from the System32 folder.
   
   NOTE: If you cannot delete the file, rename the file as Mscoree2.dll.
   
   You should be able to safely delete the renamed file after you restart your computer.
5. Run the .NET Framework Setup from the Windows Component Update CD-ROM (or from the WCU folder if you are installing by using the DVD-ROM).
6. Run Visual Studio .NET Setup again.

5.6 Setup Errors When the Registry Size Is Insufficient

If the registry is low on space, you may receive error messages similar to the following during Setup: To avoid such error messages, increase the maximum registry size limit.

NOTE: You must be logged on to the local computer as Administrator to change the size of the registry.

To change the maximum size of the computer's registry, follow these steps:

• Microsoft Windows 2000
  1. Click Start, point to Settings, click Control Panel, and then double-click the System icon.
  2. On the Advanced tab, click Performance Options, and then click Change in the Virtual Memory section.
  3. Type a new value in the Maximum registry size (MB) field.
• Microsoft Windows NT 4.0
  1. Click Start, point to Settings, click Control Panel, and then double-click the System icon.
  2. On the Performance tab, click Virtual Memory, and click Change.
  3. Type a new value in the Maximum registry size (MB) field.

5.7 Slow .NET Framework Performance After You Upgrade the Operating System

If you upgrade your operating system after you install the .NET Framework, you must repair the .NET Framework to restore performance.

To repair the .NET Framework, follow these steps:

1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
2. Click Click here for support information.
3. Open the Repair.htm file, which is installed to the version directory for the .NET Framework.
4. Follow the instructions in Repair.htm.

5.8 Microsoft Visual InterDev 6.0 Cannot Create a New Web project After You Uninstall Visual Studio .NET

After you uninstall Visual Studio .NET, you are unable to create a New Web Project in Visual InterDev 6.0.

To resolve this issue, run the Repair tool for Visual InterDev 6.0.

5.9 Install the Current Driver for Your Video Display Card

Make sure that the current driver for your video display card is installed in your computer. Outdated video display card drivers have been identified as the cause of various issues, including the following:

• Certain Gateway installation CD-ROMs provide outdated drivers for ATI RAGE 128 PRO video display cards. When you start Visual Studio .NET on a computer with an outdated video driver, the outdated video driver creates a URT Null Reference exception that causes the program to stop responding or quit (crash).
• When you attempt to rename items in a tree or list box control on a Windows NT 4.0-based computer in which an ATI 3D Rage Pro AGP video display card is installed, an outdated video driver can cause all text in the control to be rendered invisible.
• If you connect to a remote computer through Remote Desktop Connection or Terminal Services client, use Visual Studio .NET through the remote connection, and then terminate the remote session, the Visual Studio .NET development environment may stop responding or quit on the remote computer.

To prevent such issues from occurring, do the following:

Download and install the current driver. It is important to understand that the automatic update feature of your operating system may not discover a newer driver by itself. For example, if your video display card is a variety of the ATI Rage product, browse to the ATI Web site to find the most recent driver for your card, and then download and install it.

• ATI display drivers:

  http://www.ati.com/products/home-office.html

• ATI utility to determine the identity of your ATI video display card:

  https://support.ati.com/ics/support/default.asp?deptID=894

• Getting around Windows NT 4.0:

  https://support.ati.com/ics/support/default.asp?deptID=894

• Minimum requirements for AGP support in Windows NT 4.0:

  https://support.ati.com/ics/support/default.asp?deptID=894

5.10 ATI Rage Video Driver and True Color Settings

Do not use the True Color display setting when you install Visual Studio .NET on a computer with ATI Rage Video drivers installed on it. This hardware and display setting combination causes the computer to quit or stop responding when you install or run Visual Studio .NET.

To change the display setting, follow these steps:

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Display, and then click the Settings tab.
3. In the Colors list, select an option, such as High Color.

5.11 Setup User Interface Is Inaccessible with the Matrox G400 Max Dual Monitor Video Card

If the Matrox G400 Max dual-monitor video card is installed in your computer, certain areas of the user interface are inaccessible during Setup.

To resolve this issue, download the latest drivers from the following Matrox Web site:

5.12 After You Upgrade from Windows NT 4.0 to Windows 2000, Visual Studio .NET Requires a Repair

If you install Visual Studio .NET on a Windows NT 4.0-based computer, and then you upgrade to Windows 2000, certain features may not function correctly until you install Windows 2000 Service Pack 2 (SP-2).

To resolve this issue, reinstall Visual Studio .NET in repair mode.

To run repair mode, follow these steps:

1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
2. Select Visual Studio .NET, and then run step 1 to reinstall Windows Components.

5.13 Visual SourceSafe 6.0c Is Neither Windows 2000 nor Microsoft Windows XP Logo Certified

Visual Studio .NET includes Microsoft Visual SourceSafe 6.0c. This product has not been tested for Windows 2000 or Windows XP Logo Certification.

5.14 Error: Terminal Server Install Failure

When you run Visual Studio .NET Setup on a Windows 2000 Server-based computer that has Terminal Services enabled in application server mode, you may receive the following message: If you receive this message, even though you ran Setup from the Add/Remove Programs tool in Control Panel, follow these steps:

1. Click Start, and then click Run.
2. In the Run dialog box, type the following

   change user /install

   and then click OK.
3. Run Visual Studio .NET Setup.

5.15 ASP.NET Does Not Run on Computers with the /3GB Boot Option Enabled

The .NET runtime does not support the /3GB boot option, which enables user-mode programs to access 3 gigabytes (GB) of memory. Executables running under this configuration throw an exception and exit, while the ASP.NET ISAPI fails to load if this option is enabled.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base: To resolve this issue, disable this option in the Boot.ini file.

5.16 Error About Missing Files or Assemblies

When you install more than one Visual Studio product on the same computer, certain shared assemblies are present in both products. If you uninstall one of the Visual Studio products, this can break features in the remaining products when certain shared assemblies are removed. As a result, you may receive an error message similar to the following: To resolve this issue, follow these steps:

1. Click Start, point to Settings, and then click Control Panel.
2. In Control Panel, double-click Add/Remove Programs.
3. Select the remaining Visual Studio .NET product, and then run Repair.

5.17 Do Not Install Windows Installer 1.1 from the Visio CD-ROM

The Microsoft Visio CD-ROM included in the Visual Studio .NET Enterprise Architect Edition contains Windows Installer 1.1, which has not been signed with Microsoft Authenticode. Because Visual Studio .NET Setup installs Windows Installer 2.0, the earlier version of Windows Installer on the Visio CD-ROM will not be installed on computers on which Visual Studio .NET is installed.

Microsoft does not recommend that you install Windows Installer 1.1 directly from the Visio CD-ROM on older operating systems (Microsoft Windows 95, Microsoft Windows 98, and Windows NT 4.0) on which Visual Studio .NET is not installed.

5.18 Setup Fails with Asian Characters in the TEMP Path

If your user name contains Asian characters, you may receive the following error message: To resolve this issue, follow these steps:

1. On the desktop, right-click My Computer, and then click Properties on the shortcut menu.
2. On the Advanced tab, click Environment Variables.
3. In the User variables pane, click the variable named TEMP, and then click Edit.
4. In the Variable Value box, type a value that does not contain Asian characters or reference an environment variable that contains Asian characters.
5. Repeat steps 3 and 4 for the variable named TMP.
6. Click OK to save the new value.
7. Restart Setup.

5.19 "Digital Signature Not Found" Error Message in Windows Component Update

When you run the Visual Studio .NET Windows Component Update, you may receive the following error message when you install Microsoft Data Access Components 2.7 if Microsoft Data Access Components 2.6 SP2 is already installed: To resolve this issue, follow these steps:

1. Click OK to dismiss the digital signature error.
2. Click Done to dismiss the Setup Partially Complete page.
3. If Setup prompts you to reboot, click Reboot Now.
4. Click link 1, Windows Component Update, to reinstall Microsoft Data Access Components 2.7.
5. Continue with Visual Studio .NET Setup after the Windows Component Update completes successfully.

6 API Changes

Application programming interfaces (APIs) in the .NET Framework have been changed between the release of Visual Studio .NET Beta 2 and the final release of Visual Studio .NET. The document named APIChangesBeta2toRTM.htm lists these changes and is available in the \docs subfolder of the installed .NET Framework software developer's kit (SDK).

6.1 Process and Request Identity in ASP.NET

In a default installation on Windows 2000 and Windows XP-based computers, ASP.NET runs Web application code in a worker process. The identity of this process defaults to an unprivileged local account called the ASPNET account.

In beta releases of ASP.NET, the process identity is System, a powerful administrative account with many privileges on the computer. To provide a less-privileged default installation, the weaker account is now used and is suitable for use in many Web applications.

However, in some cases, ASP.NET applications developed with beta versions of ASP.NET may require changes to work with the new process identity. For additional details about this change, and to review the ASP.NET documentation, browse to the following Microsoft Web site:

7 Security Guidelines

For the latest information about security guidelines, browse to the following Microsoft Web site:

7.1 Debugger User Account Group

The Debugger user account group permits users who do not belong to the Administrator group on a computer to debug their own processes. Be sure to add only trusted users to this group.

8 How to Deploy the .NET Framework

Browse to the following Microsoft Web site for information about how to deploy the .NET Framework with your application:

9 Known Product Issues

For comprehensive information about all known issues for Visual Studio .NET, browse to the following Microsoft Microsoft Web site: