Visual Studio .NET 2003 Readme (Part 2)

This article contains Part 2 of the Microsoft Visual Studio .NET 2003 Readme file. For Part 1 of the Readme, click the following article number to view the article in the Microsoft Knowledge Base:

4. Installing Visual Studio .NET 2003

To install Visual Studio .NET 2003

1. Close all open applications to prevent additional reboots during setup.
2. Insert the disc labeled Visual Studio .NET 2003 CD1.
   
   Autorun starts Setup.exe. If Autorun is disabled, run Setup.exe from the root of the installation CD.
   
   The setup program scans your disk for installed components. If the scan determines that the system requires a component update, Step 1: Install Visual Studio .NET 2003 Prerequisites is available in the Installation dialog box. Select Step 1 to update the system components. If a component update is not required, this option is not available. After updating the system components, the Installation dialog box enables Step 2: Install Visual Studio .NET 2003. Select Step 2 to install Visual Studio .NET 2003.
3. If you are installing a Web server and are asked to install IIS, see section 4.2 for complete instructions.

4.1. Facilitating Setup Over a Network

Visual Studio .NET 2003 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 .NET 2003 for installation from a network share.

Example procedure for sharing the installation files from CDs

1. Create a folder (for example, VS2003) on the server.
2. Create three subfolders, named PRE, VS, and MSDN within the top-level folder. For example:
   
   VS2003\PRE
   VS2003\VS
   VS2003\MSDN.
3. Copy the contents of the CD labeled Visual Studio .NET 2003 Prerequisites to the subfolder named PRE.
   
   Copy the contents of all CDs labeled Visual Studio .NET 2003 to the subfolder named VS. If prompted, overwrite existing files.
   
   Copy the contents from all the CDs labeled MSDN Library for Visual Studio .NET 2003 to the subfolder named MSDN. If prompted, overwrite existing files.
4. Open Setup.ini in the VS subfolder using a text editor, such as Notepad.
5. In the [Baseline] section, change the line that starts with "DIR=" as follows:
   
   [Baseline]
   DIR=..\PRE
   FileName=setup.exe
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 Visual Studio .NET 2003 Prerequisites and 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.
11. Share the VS2003 folder on the network and set the appropriate security settings. The path to Visual Studio .NET 2003 setup from the network looks as follows:
    
    \\[servername]\VS2003\VS\setup.exe
    Note Setup fails if any path and file name combination exceeds 260 characters. The maximum length of a path in Visual Studio is 221 characters; accordingly, 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 may fail if the folder names in this path include embedded spaces, for example: "\\[servername]\VS 2003\MSDN\" or "\\[servername]\VS2003\Visual Studio\".
    
    Note Visual SourceSafe® and Visio® are not part of Visual Studio .NET 2003 setup. However, you may also copy the contents of the Visual SourceSafe and Visio CDs to separate folders on your server to facilitate setup of these products over a network as separate installations.

4.2. Configuring a Remote Web Server for ASP.NET Projects

To work with Web applications in Visual Studio .NET 2003, your development computer and Web server must be properly configured.

Requirements

Following are the operating system requirements for working with Web Forms and XML Web services in Visual Studio .NET 2003:

• The Web server must be running Windows 2000, Windows XP, or Windows Server 2003. Computers running Windows 95, Windows 98, Windows Me, or Windows NT 4.0 are not supported.
• It is recommended that the Web server be installed on a computer formatted with the NTFS file system. While supported by Visual Studio .NET 2003, FAT and FAT32 are not as secure as NTFS.
• The Web server must be running Internet Information Services (IIS) version 5.0 or 6.0. For details, see Setup\WebServer.htm on Visual Studio .NET 2003 CD1.

Configuring the Server Computer

If you are developing on one computer with Visual Studio .NET 2003 and want to deploy your Web applications to a remote Web server computer, you must configure the server computer properly. Doing so requires installation of some Visual Studio .NET 2003 components on the Web server computer.

Note If you are using your development computer as the Web server, you do not need to follow this procedure; installing Visual Studio .NET 2003 on your computer configures it properly.

To configure a separate Web server computer for Visual Studio .NET 2003

1. Run Visual Studio .NET 2003 setup on the Web server computer and perform Step 1 to install the Visual Studio .NET 2003 Prerequisites.
   
   This installs the Microsoft .NET Framework on the server computer. When this step is complete, the setup process returns to Step 2 of the Visual Studio .NET 2003 installation.
2. Start Step 2 of the setup process. In the left pane of the setup window are a number of options for the installation. You should:
   1. Clear the selection of all options except Server Components.
   2. Expand the Server Components node and select Web Development and Remote Debugger.
   3. Then click Install Now to proceed with installation.
3. Verify that FrontPage® Server Extensions are configured. For details, see Setup\WebServer.htm on Visual Studio .NET 2003 CD1.
4. Add users who will be creating Web projects to the VS Developers group.

Important debugging information

• To debug an ASP.NET application, you must first determine the configuration of the server to identify in which process the application is running. On IIS 5.0, the process to debug may be either aspnet_wp.exe (the default ASP.NET worker process) or inetinfo.exe (if the application has been configured to run in process). On IIS 6.0, which is part of Windows Server 2003, the default is to run in w3wp.exe, the IIS worker process. If you are using IIS5-Compat mode, then the instructions for IIS 5.0 apply. Regardless of the process under which the ASP.NET application is running, you must be the Administrator user or a member of the Administrators group. You may also change the process identity to run under a user account. For IIS 5.0 you must edit the machine.config file for aspnet_wp.exe. For IIS 6.0, you must edit the app pool configuration for w3wp.exe. Furthermore, you must change some Access Control Lists (ACL) for the application to run properly under a user account. Refer to http://support.microsoft.com (http://support.microsoft.com/) for updated information. The aspnet_wp.exe runs as "machine" or ASPNET by default, while w3wp.exe runs as "NETWORK SERVICE" by default.

4.3. Installing Microsoft SQL Server Desktop Engine (MSDE)

Visual Studio .NET 2003 does not include Microsoft SQL Server Desktop Engine (MSDE). To download MSDE, go to http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en) .

Caution If you plan on installing Application Center 2000, you must install Application Center 2000 before installing MSDE.

4.4. Installing the Remote Debugger

If you intend to debug processes on a remote machine, you must install the Remote Debugger. For details, see RemoteComponents.htm at the root of Visual Studio .NET 2003 CD1.

4.5. Uninstalling Visual Studio .NET 2003

To uninstall Visual Studio .NET 2003, use the Add/Remove Programs Control Panel.

Uninstalling Visual Studio .NET 2003 Prerequisites

Uninstalling Visual Studio .NET 2003 does not uninstall components installed by Visual Studio .NET Prerequisites. For components that offer individual uninstall, use the Add/Remove Programs Control Panel.

5. Known Installation Issues

5.1. Cannot find original installation location

When Setup is run from the Change or Remove Programs section of the Add/Remove Programs Control Panel, you may receive the following error message when adding features: This message appears because the CD or network location from which Visual Studio .NET 2003 was installed is no longer present. To add features, insert the disc or reconnect to the network location, and then return to Setup.

5.2. Error 1308: Source file not found

This message is displayed when installing Visual Studio .NET 2003 from a shared CD-ROM drive or installing on some systems with multiple CD-ROM drives.

To continue with setup, insert the next CD into the drive that originally had CD1, and then click Retry. Repeat for each CD when the error message appears.

5.3. Error messages when running setup

When running Setup, you may see the error message "A problem has been encountered while loading the setup components. Canceling setup." This error occurs when critical Setup files are missing. If you are installing from a network image, recopy the CDs to make sure all files are present.

5.4. Error 1711: An error occurred while writing installation information to disk.

This error may occur if you run setup with less than 900 MB of free space on your system drive.

To resolve this issue

• Free space on your system drive so you have at least 900 MB free and then run setup again.

5.5. Setup errors when registry size is insufficient

If the registry is low on space, errors such as "Error: could not locate INF file" could occur during setup.

To avoid such errors, increase the maximum registry size limit.To change the maximum size of the computer's registry

1. From the Start menu, point to Settings, click Control Panel, and then double-click the System icon.
2. On the Advanced tab, click Performance Options, and click Change in the Virtual memory section.
3. Type a new value in the Maximum registry size (MB) field.

5.6. An upgrade of the operating system requires a repair of the .NET Framework.

If you upgrade your operating system after installing the .NET Framework, you must repair the .NET Framework.

To repair the .NET Framework

1. From the Start menu, point to Control Panel, and then click Add/Remove Programs.
2. In the Currently installed programs pane, select Microsoft .NET Framework 1.1.
3. Click Click here for support information.
4. Open the file named RepairRedist.htm, which is installed to the version directory for the .NET Framework; [system drive]\WINDOWS\Microsoft.NET\Framework\v1.1.4322\1033.
5. Follow the instructions in RepairRedist.htm.
   Note The command-line code for repairing the .NET Framework redistributable is: [Installation Source]\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi

5.7. After uninstalling Visual Studio .NET, Visual InterDev® 6.0 cannot create a new Web project.

After uninstalling Visual Studio .NET 2003, you will be unable to create a new Web project in Visual InterDev 6.0.

To resolve this issue

• Run repair/reinstall for Visual InterDev 6.0.

5.8. Install the current driver for your video display card.

Make sure that the current driver for your video display card is installed on your machine. Outdated video display card drivers have been identified as the cause of problems such as the following:

• Certain Gateway install CDs provide outdated drivers for ATI RAGE 128 PRO video display cards. When you start Visual Studio .NET 2003 on such machines, the outdated video driver creates a URT Null Reference exception that crashes the program.
• If you connect to a remote computer via Remote Desktop Connection or Terminal Services client, use Visual Studio .NET 2003 through the remote connection, and terminate the remote session, the Visual Studio .NET Development Environment may be frozen or unusable on the remote machine.

To prevent such problems

Download and install the current driver. It is important to realize 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, go to the ATI web site, find the most recent driver for your card, download and install it.

• ATI Display Drivers http://support.amd.com/us/Pages/AMDSupportHub.aspx (http://support.amd.com/us/Pages/AMDSupportHub.aspx)
• ATI utility to determine the identity of your ATI video display card http://support.amd.com/us/Pages/AMDSupportHub.aspx (http://support.amd.com/us/Pages/AMDSupportHub.aspx)

5.9. ATI Rage video driver and True Color settings

Machines with ATI Rage Video drivers should not use the True Color display setting when installing Visual Studio .NET 2003. This hardware and display setting combination causes a crash when installing or running Visual Studio .NET 2003.

To change the display setting

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

5.10. Setup user interface is inaccessible when using Matrox G400 Max dual Monitor.

Users of the Matrox G400 Max dual Monitor video card may find that certain areas of the user interface are inaccessible during setup. To correct this problem, download the latest drivers from the Matrox Web site at http://www.matrox.com (http://www.matrox.com) .

5.11. Visual SourceSafe 6.0d is neither Windows 2000 nor Windows XP Logo Certified.

Visual Studio .NET 2003 Enterprise Developer and Visual Studio .NET Enterprise Architect editions include Visual SourceSafe 6.0d. This product has not been tested for Windows 2000 or Windows XP Logo Certification.

5.12. Error about missing files or assemblies

When installing more than one Visual Studio product on the same machine, certain shared assemblies are present in both products. Uninstalling one of the Visual Studio products can break features in the remaining products when certain shared assemblies get removed. The resulting error looks like "File or assembly name XXX, or one of its dependencies, was not found."

To resolve this issue

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

5.13. Do not install Windows Installer 1.1 from the Visio installation CD.

The Visio CD 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 will not be installed on machines with Visual Studio .NET installed.

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

5.14. Visual Studio Analyzer integration with Windows Management Instrumentation (WMI) requires compilation of MOF file.

To exchange events between Visual Studio Analyzer and WMI, you must compile an MOF file with the WMI MOF compiler (mofcomp.exe), as explained below. If your operating system is one of the Windows 2000 family, you must type the following line at the command prompt:
"%SYSTEMROOT%\system32\wbem\mofcomp.exe [Visual Studio 2003 installation directory]\Common7\Tools\Analyzer\Bridges\WMI\appprof2k.mof"

If your operating system is one of the Windows XP or Windows Server 2003 families, you must type the following line at the command prompt:

"%SYSTEMROOT%\system32\wbem\mofcomp.exe [Visual Studio 2003 installation directory]\Common7\Tools\Analyzer\Bridges\WMI\appprof.mof"

5.15. Solution and Project file formats have changed in Visual Studio .NET 2003.

The formats of the solution and project files in Visual Studio .NET 2003 are different from the corresponding formats in Visual Studio .NET 2002. The Visual Studio .NET 2003 formats are not backwards compatible. When you first open a previous version's solution or project file in Visual Studio .NET 2003, you are prompted to convert. After conversion, you cannot open the files in the previous version of Visual Studio. For additional details, see the help topic available from the Conversion dialog box.

5.16. Application Center Test not available when Visual Studio .NET is already installed

If you have installed Visual Studio .NET 2002 with the Application Center Test (ACT) feature, then you will not be able to install the Visual Studio .NET 2003 ACT feature. On a single machine, you can have the ACT feature installed with Visual Studio .NET 2003 or Visual Studio .NET 2002, but not both.

To resolve this issue

1. In the Windows Control Panel, double-click Add/Remove Programs.
2. Choose Visual Studio .NET 2002, and then click Change/Remove.
3. In the Visual Studio .NET Setup window, click link 2 Visual Studio .NET.
4. Click the Add or Remove Features link.
5. Under Enterprise Development Tools, clear Application Center Test.
6. Click Update Now! to remove the Application Center Test Feature.
7. When setup is complete, click Done.
8. Return to the Add or Remove Programs dialog box.
9. Choose Visual Studio .NET 2003, and then click Change/Remove.
10. In the Visual Studio .NET Setup window, click link 2 Visual Studio .NET.
11. Click the Add or Remove Features link.
12. Under Enterprise Development Tools, select Application Center Test.
13. Click Update Now! to add the feature.
14. When setup is complete, click Done.

5.17. Uninstall Microsoft .NET Compact Framework Betas from the device before installing the final version on the device.

If a beta version of the .NET Compact Framework (Tech Preview, Beta1 or Visual Studio .NET Codename Everett Beta 1) is installed on a device, uninstall it before installing the release version of .NET Compact Framework Beta2. A beta version could have been installed manually or as part of debugging and deploying an application with Visual Studio .NET 2002 or Visual Studio .NET 2003.

5.18. Installing Help for Visual Studio .NET 2003

The MSDN Library provides Help for Visual Studio .NET 2003. If you do not install the MSDN Library, F1 Help, the Dynamic Help window, the index, search, and the table of contents will not provide assistance about using the Visual Studio .NET 2003 Integrated Development Environment (IDE) or any languages.

To resolve this issue, install Help for Visual Studio

1. From the Start menu, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
2. In the Windows Control Panel, double-click Add/Remove Programs.
3. Choose Visual Studio .NET 2003, and then click Change/Remove.
4. In the main setup dialog box, click Step 3.
   As an alternative, you can skip these steps, insert the MSDN CD included with Visual Studio .NET 2003, and run MSDN setup.

5.19. Upgrading Designer RESX files from SDE Beta 1

Designer-generated RESX files from Smart Device Extensions Beta 1 may not work with smart device projects in Visual Studio .NET 2003.

To resolve this issue

• Delete the legacy RESX file and reopen your forms in the Designer to automatically generate the correct RESX file. RESX files are files in your project that have an extension "resx".

5.20. Installing MSDN before Visual Studio .NET 2003 locks the Visual Studio .NET 2003 install path.

If you install MSDN Library for Visual Studio .NET 2003 before Visual Studio .NET 2003, you can only install Visual Studio .NET 2003 to the following location: [System Drive]:\Program Files\Microsoft Visual Studio .NET 2003 folder.

To resolve this issue

• Install Visual Studio .NET 2003 before MSDN.

5.21. Vertical upgrade support: Maintaining the Visual Studio IDE

The Visual Studio integrated development environment (IDE) is part of the installation of several product editions, which are categorized according to the following list.

1. Visual Basic .NET 2003 Standard
   Visual C# .NET 2003 Standard
   Visual C++ .NET 2003 Standard
   Visual J# . NET 2003 Standard
2. Visual Studio .NET 2003 Trial Edition
   Visual Studio .NET 2003 Academic
   Visual Studio .NET 2003 Professional
3. Visual Studio .NET 2003 Enterprise Developer
   Visual Studio .NET 2003 Enterprise Architect

You might install the IDE as part of a product in one group, for example Visual Basic .NET 2003 Standard, and later install a product from a higher numbered group, for example Visual Studio .NET 2003 Trial Edition. In these instances, you have two installation options:

• Uninstall the product from the lower numbered group and install the product from the higher numbered group.
  
  -or-
• Install the product from the higher numbered group without uninstalling the other product.

Although both options work, the second option requires more disk space.

5.22. Error 2349: Copy Resumed With Different Info

This message displays when a network error occurs during setup.

To resolve this issue

• Verify your network is working correctly and restart setup.

5.23. Custom machine configuration settings are not preserved when upgrading the .NET Framework.

When upgrading to a newer version of the .NET Framework, custom machine configuration settings are not automatically copied from the older version to the newer version. By design, installation of a new version of the .NET Framework creates a new default machine configuration file during setup.

To resolve this issue

1. Search for a file named machine.config.
   The result displays multiple instances of the file. Each file is in a CONFIG directory that is qualified by the version number of the .NET Framework.
2. Copy custom settings from the old version of machine.config to the new version of machine.config.

5.24. Setup may fail when antivirus and personal firewall software are running.

Antivirus and personal firewall software might cause Visual Studio .NET 2003 and .NET Framework setup to fail. This problem affects systems running Windows 2000, Windows XP, or Windows Server 2003. For example:

• In some cases, if you are running an antivirus program while setup runs, the antivirus program may display warnings. These warnings occur when Visual Studio .NET or .NET Framework setup runs scripts that access file system objects. It is safe to allow the scripts to run.
• In other cases, firewall software may interfere with configuration of certain services during Visual Studio .NET or .NET Framework setup. For example, firewall software may cause setup to stop responding when configuring IIS services, such as the World Wide Web Publishing service, FTP Publishing service, and Simple Mail Transport Protocol (SMTP) service.

To resolve this issue

• For the latest information on troubleshooting antivirus and personal firewall issues during installation, see the KB article at http://go.microsoft.com/fwlink/?LinkId=12236 (http://go.microsoft.com/fwlink/?LinkId=12236) .

5.25. Failure of FrontPage 2000 Web Client Extensions Installation

A typical installation of Visual Studio .NET 2003 installs FrontPage 2000 Web Client Extensions from the Visual Studio .NET 2003 Prerequisites CD. In some instances, installation of FrontPage 2000 Web Client Extensions may fail. Consequently, you might need to install FrontPage 2000 Web Client Extensions directly.

To resolve this issue

1. Insert the Visual Studio .NET 2003 Prerequisites CD.
2. On the Windows Start menu, click Run, and type [CD Drive]:\weccom.msi
3. Follow the directions in the FrontPage 2000 Web Client Extensions setup dialog box.

On Windows XP Home Edition:

Setup may prompt for the Windows XP Professional Edition CD. Insert either the Windows XP Home Edition or the Windows XP Professional Edition CD.

On Windows XP Home Edition or Windows XP Professional Edition with Service Pack 1 installed:

Setup may prompt for the Windows XP SP1 CD. Insert the Windows XP Operating System CD rather than the SP1 CD when prompted for operating system source media.

• Copy Fp4autl.dll, Fpencode.dll, and Fp4awel.dll from \i386\Fp40ext.cab.
• To [Local drive]:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\bin.

5.26. Installing Visual Studio .NET 2003 before installing ASP.NET on Windows Server 2003 prevents creation of Visual J# .NET Web applications.

The Visual J# .NET Redistributable Package is installed as part of the Visual Studio .NET Prerequisites setup during Visual Studio .NET 2003 installation. When you install Visual Studio .NET 2003 before installing ASP.NET, the Visual J# .NET Redistributable Package setup does not update the Internet Information Services (IIS) ScriptMaps metabase property to prevent J# files (with .jsl, .java, and .vjsproj extensions) from being downloaded. On Windows Server 2003, installing IIS does not install ASP.NET by default. Installing Visual Studio .NET 2003 before installing ASP.NET on Windows Server 2003 can lead to this situation.

To resolve this issue

• Uninstall, and then reinstall the Visual J# .NET Redistributable Package.

To uninstall Visual J# .NET Redistributable Package

1. From the Start menu, point to Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Choose Visual J# .NET Redistributable Package 1.1, and then click Remove.

To reinstall Visual J# .NET Redistributable Package

1. For the DVD version of Visual Studio .NET 2003, insert the DVD.
2. From the Start menu, click Run and type:
   <DVD Drive>:\wcu\JSharpRedistCore\vjsredist.exe
   -or-
3. For the CD version of Visual Studio .NET 2003, insert the Visual Studio .NET Prerequisites CD.
4. From the Start menu, click Run and type:
   <CD Drive>:\JSharpRedistCode\vjsredist.exe.

5.27. Do not install different language versions of Visual Studio .NET 2003 and Visual Studio .NET 2002 on the same computer.

Visual Studio .NET functionality is impaired when Visual Studio .NET 2003 is installed on a computer with a different language version than Visual Studio .NET 2002. For example, do not install an English version of Visual Studio .NET 2003 on a computer that has a Japanese version of Visual Studio .NET 2002 installed.

To resolve this issue

• Install the language version of Visual Studio .NET 2003 that matches your existing Visual Studio .NET 2002 installation.
  
  -or-
• Uninstall Visual Studio .NET 2002, and then reinstall Visual Studio .NET 2002 with same language version as your intended Visual Studio .NET 2003 installation.

5.28. After upgrading the operating system to Windows XP, repair of .NET Framework yields an error.

After upgrading your operating system to Windows XP, repair of .NET Framework may display an error message, "'Error 1931. Windows Installer Service can't update \WBEM\wmiutils.dll. This file is protected by Windows."

To resolve this issue

• Click OK and repair will complete.

6. API Changes

For a list of the changes and additions to the class library for the .NET Framework version 1.1, see http://msdn2.microsoft.com/en-us/library/d11h6832(VS.71).aspx (http://msdn2.microsoft.com/en-us/library/d11h6832(VS.71).aspx) .

7. Security Guidelines

For the latest security information, check the .NET Framework Security Web site at http://go.microsoft.com/fwlink/?LinkId=5588 (http://go.microsoft.com/fwlink/?LinkId=5588) .

7.1. Debugger User Account Group

Members of the Debugger Users group can debug their own processes on a machine even if the same users do not belong to the Administrators group on a machine. Add only trusted users to the Debugger Users group.

8. Deploying the .NET Framework

Visit http://go.microsoft.com/fwlink/?LinkId=5201 (http://go.microsoft.com/fwlink/?LinkId=5201) for information on deploying the .NET Framework with your application.

9. Known Product Issues

For Visual Studio .NET 2003 known issues, see Visual Studio .NET 2003 Known Issues (http://go.microsoft.com/fwlink/?LinkId=8793) .

10. End-User License Agreement Location

The End-User License Agreement (EULA) can be found in the product name subdirectory of the Microsoft Visual Studio .NET 2003 installation directory. The name of the file is EULA.txt.

For example, if you install Visual Studio .NET Enterprise Architect, the file named EULA.txt is in the following location:

[Drive Letter]:\Program Files\Microsoft Visual Studio .NET 2003\Visual Studio .NET Enterprise Architect – English.