Microsoft KB Archive/312779

= Visual Studio .NET 2002 Readme (Part 1) =

Article ID: 312779

Article Last Modified on 3/29/2007

-

APPLIES TO


 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Academic Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer

-



This article was previously published under Q312779



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

316250 Visual Studio .NET Readme (Part 2)



Microsoft Visual Studio .NET Readme
This document contains last-minute notes for installing Visual Studio .NET. See http://support.microsoft.com/default.aspx?scid=fh;en-us;vsnet for the latest product support information.

1 Getting Started
After you have installed Visual Studio .NET, the End User License Agreement (EULA.txt) for Visual Studio .NET is available for reference on CD1 or DVD in the Setup folder.

1.1 Related Readmes
In addition to this Visual Studio .NET product readme, Visual Studio .NET includes other readme documents that contain information pertinent to specific product areas. The following list contains the names of related readme documents and their locations on supplied media.

2 System Requirements
The tables below list requirements for different installation options of Visual Studio .NET. The &quot;NOTES&quot; following the tables apply to both tables.

System Requirements for Installing All Visual Studio .NET Versions

System Requirements for Installing Individual Languages

NOTES:
 * 1) Performance has not been tuned for minimum system configuration. Increasing your RAM above the recommended system configuration increases your performance specifically when running multiple applications, working with large projects, or doing enterprise-level development.
 * 2) When you start the Visual Studio .NET 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 required amount of space identified in the tables above is available on your system drive regardless of the application's location, and ensure that additional space is available on the drive on which you install the application. Custom installation choices may require more or less hard-disk space.
 * 3) Windows 95, Windows 98, Windows 98 Second Edition, and Windows ME are not supported platforms for design and development for Visual Studio .NET. You can deploy applications and remotely debug applications in the Windows 98 and Windows ME platform environments.
 * 4) Microsoft Windows 2000 Datacenter Server is not a supported operating system.
 * 5) A CD-ROM or DVD-ROM is required based on the type of media provided with the product.

2.1 Visual Studio 6.0 and Visual Studio .NET Compatibility
Both Visual Studio .NET and Visual Studio 6.0 can be installed on the same computer and run at the same time. Once you have installed the Visual Studio .NET documentation, see Upgrading Applications (http://msdn2.microsoft.com/en-us/library/dy163kx7(vs.71).aspx) for more information on application compatibility and upgrading.

3 Preparing to Install Visual Studio .NET

 * Before installing Visual Studio .NET, verify that you have met the system requirements and follow the instructions below for preparing to install Visual Studio .NET.
 * If you use Microsoft Office XP Developer, you must install it prior to .NET Framework SDK and MSDN for Visual Studio .NET. Otherwise the Office Developer Help documentation will not be available.
 * If you are running an operating system with Turkish or Azeri set as the active locale, see the .NET Framework SDK readme at http://msdn2.microsoft.com/en-us/vstudio/aa718689.aspx before installing. In version 1 of the .NET Framework, there are known issues for the Turkish and Azeri locales.

3.1 Uninstalling Pre-release Versions of Visual Studio .NET
WARNING: If you have previously installed any pre-release versions of the .NET Framework or Visual Studio (Release Candidate, Beta 2, Beta 1, or PDC Technology Preview) on your computer, you must complete the following steps to uninstall the previous releases.

To uninstall Visual Studio .NET Beta 2 or later pre-release versions


 * 1) From the Start menu, choose Settings and then Control Panel.
 * 2) Choose Add/Remove Programs and then choose Change or Remove Programs.
 * 3) If present, select Visual Studio .NET and choose Change/Remove. Otherwise, skip to step 7.
 * 4) Click link 2, Visual Studio .NET.
 * 5) Click Uninstall Visual Studio .NET to begin uninstall.
 * 6) After uninstall completes for Visual Studio .NET Beta 2, return to the Add/Remove Programs window.
 * 7) Select Microsoft .NET Framework and choose Change/Remove.
 * 8) Answer Yes to proceed with removal.
 * 9) After removing Microsoft .NET Framework, return to the desktop.
 * 10) Right-click My Computer and select Manage from the shortcut menu.
 * 11) Expand the Services and Applications node and select Services.
 * 12) Double-click .NET Framework Support Service.

NOTE: If the service is unlisted, proceed to step 14.
 * 1) Change the Startup type to Disabled.
 * 2) Restart your machine.

To uninstall Visual Studio .NET 7.0 Beta 1


 * 1) From the Start menu, choose Settings and then Control Panel.
 * 2) Choose Add/Remove Programs and then choose Change or Remove Programs.
 * 3) Select Visual Studio .NET 7.0 Enterprise and choose Change/Remove.
 * 4) Click link 2, Visual Studio .NET.
 * 5) Click Uninstall Visual Studio .NET 7.0 Enterprise to begin uninstall.
 * 6) After uninstall completes for Visual Studio .NET 7.0 Beta 1, return to the Add/Remove Programs window.
 * 7) Select Microsoft .NET Framework SDK and choose Change/Remove.
 * 8) Answer Yes to proceed with removal.

To uninstall Visual Studio 7.0 PDC Technology Preview

 From the Start menu, choose Run. In the Run dialog box, type the following:

msiexec.exe /x {33334F07-0C6B-11D3-A51D-00A0C9231BA1} NOVSUI=1 Answer Yes, when prompted, to proceed with the removal of Visual Studio .NET PDC Technology Preview. In the Run dialog box, type the following:

msiexec.exe /x {62EDCF3C-69F4-11D3-A521-00A0C9231BA1}

 Answer Yes, when prompted, to proceed with removal of the Pre-release Bootstrap for Visual Studio .NET PDC Technology Preview. From the Start menu, choose Settings and then Control Panel. Choose Add/Remove Programs and then choose Change or Remove Programs.</li> Select Microsoft NGWS SDK and choose Change/Remove.</li> Answer Yes to proceed with removal.</li> Remove all files from N:\Documents and Settings\All Users\Application Data\Microsoft Help. This step ensures the removal of PDC release documentation.</li></ol>

3.1.1 Uninstalling Deployed Applications
If you have created applications with a pre-release version of Visual Studio .NET and deployed those applications using the .NET Framework merge module provided by the Visual Studio .NET deployment feature, you must uninstall those applications before installing Visual Studio .NET.

To uninstall deployed applications, use the Add/Remove Programs feature in the Control Panel.

If you do not uninstall deployed applications, Visual Studio .NET installation will not proceed until all instances of the .NET Framework are uninstalled.

3.2 Uninstalling Visual Studio Analyzer 6.0
The version of Visual Studio Analyzer shipping with Visual Studio .NET Enterprise edition is not compatible with Visual Studio Analyzer 6.0.

If you are installing Visual Studio Analyzer that is included with Visual Studio .NET Enterprise edition on a computer that has Visual Studio Analyzer 6.0 installed, uninstall Visual Studio Analyzer 6.0 before installing Visual Studio .NET. Visual Studio Analyzer is part of the default Visual Studio .NET Enterprise edition installation.

If you have mistakenly installed both versions on the same computer, you will not be able to collect events in Visual Studio Analyzer. You must uninstall one version of the product and follow the instructions below to repair the remaining installed version.

To repair Visual Studio Analyzer after uninstalling Visual Studio Analyzer 6.0


 * 1) Reboot your computer.
 * 2) Run RegisterAnalyzerv7.bat from  \Common7\Tools\Analyzer.

To repair Visual Studio Analyzer 6.0 after uninstalling Visual Studio Analyzer
 * 1) Before uninstalling Visual Studio Analyzer, copy the following files FROM  \Common7\Tools\Analyzer TO  \Common\Tools\VS-ENT98\Vanalyzr:
 * 2) * RegisterAnalyzerv6.bat
 * 3) * VSAReg.exe
 * 4) After uninstalling Visual Studio Analyzer, run RegisterAnalyzerv6.bat from  \Common\Tools\VS-ENT98\Vanalyzr.

4 Installing Visual Studio .NET
To install Visual Studio .NET


 * 1) Close all open applications to prevent additional reboots during Setup.
 * 2) Insert the disc labeled Visual Studio .NET CD1 or DVD. Autorun starts Setup.exe. If Autorun is disabled, run Setup.exe from the root of the installation CD or DVD.

The Setup program scans your disk for installed components. If the scan determines that the system requires a component update, Step 1: Install Windows Component Update, 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. Select Step 2 to install Visual Studio .NET.

NOTE: If you are running an anti-virus program, such as Norton AntiVirus 2001, while Setup runs, warnings may be displayed because Setup runs scripts that access the file system object. It is safe to allow the scripts to run.

To register Visual Studio .NET Visit the Visual Studio .NET Internet registration site at http://msdn.microsoft.com/vstudio/register/vsnet/.

4.1 Facilitating Setup over a Network
The following procedures illustrate how to prepare Visual Studio .NET for installation from a network share.

To share the installation files from the CDs


 * 1) Create a top-level folder (for example, VS7) on the server.
 * 2) Create a folder named WCU within the top-level folder (for example, VS7\WCU).
 * 3) Copy the contents of the CD labeled Visual Studio .NET Windows Component Update to the folder named WCU.
 * 4) Create a folder named VS within the top-level folder.
 * 5) Copy the contents of the remaining Visual Studio .NET CDs to the VS7\VS folder (choose to overwrite existing files).

NOTE: Optionally, you may also copy the contents of other CDs, such as SourceSafe, Visio, and so on, to separate folders for setup over a network.
 * 1) Open setup.ini in the VS folder using a text editor, such as Notepad.
 * 2) In the [Baseline] section, change the line that starts with &quot;DIR=&quot; to DIR=..\WCU . For example:

''[Baseline]

DIR=..\WCU

FileName=setup.exe''
 * 1) Save your changes and close the file.

Completing this step prevents disk-swapping requests during Setup and informs Setup of the correct path to the Windows Component Update disk.
 * 1) Create a network share to the VS7 folder and establish the appropriate security settings. The path to Visual Studio .NET Setup from the network is now:

\\ \VS7\VS\setup.exe

NOTE: When installing, 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 install location should contain fewer than 39 characters.

To share the installation files from the DVD


 * 1) Copy the contents of the DVD into a top-level folder named VS7.

NOTE: Optionally, you may also copy the contents of other CDs, such as SourceSafe, Visio, and so on, for setup over a network.
 * 1) Create a network share to the VS7 folder and establish appropriate security settings. The path to Visual Studio .NET Setup from the network is now:

\\ \VS7\setup.exe

NOTE: When installing, 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 install location should contain fewer than 39 characters. Examples:

Not valid

\\products\corporate\licenses\DeveloperTools\Visual Studio\Visual Studio .NET\NetSetup

Valid

\\products\DeveloperTools\Visual Studio .NET\NetSetup

4.2 Configuring a Remote Web Server for ASP.NET Projects
To work with Web applications in Visual Studio .NET, 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:
 * 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, 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 CD1 or DVD.

Configuring the Server Computer

If you are developing on one computer with Visual Studio .NET 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 components on the Web server computer.

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

To configure a separate Web server computer for Visual Studio .NET <ol> Run Visual Studio .NET Setup on the Web server computer and perform Step 1 to install the Windows Component Update. This installs the .NET Framework on the server computer. When this step is complete, the Setup process returns to Step 2 of the Visual Studio .NET installation.</li> 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: <ol style="list-style-type: lower-alpha;"> Clear the selection of all options except Server Components.</li> Expand the Server Components node and select Web Development and Remote Debugger.</li> Click Install Now to proceed with installation.</li></ol> </li> Verify that FrontPage Server Extensions are configured. For details, see Setup\WebServer.htm on Visual Studio .NET CD1 or DVD.</li> Add users who will be creating Web projects to the VS Developers group.</li></ol>

Important debugging information

To debug an application running under aspnet_wp.exe, you must be Administrator or a member of the Administrators group or you must edit the machine.config file for aspnet_wp.exe so that aspnet_wp.exe runs under a user account. To debug an application running under inetinfo.exe, you must be Administrator or a member of the Administrators group on the machine running inetinfo.exe. This is the case because ASP.NET applications run under inetinfo.exe (the IIS process) or the ASP worker process aspnet_wp.exe, depending on security settings. The aspnet_wp.exe process runs as SYSTEM by default.

4.3 Installing SQL Server Desktop Engine (MSDE)
If you selected the SQL Server Desktop Engine feature during Setup, all files required to install the SQL Server Desktop Engine (MSDE) are installed on the machine. The following procedure illustrates how to configure and install MSDE.

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

To set the MSDE instance name

NOTE: You may skip these steps and accept the default instance name, VSdotNET.
 * 1) From the Start menu, choose Run.
 * 2) Type C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Samples\Setup\msde and click OK.
 * 3) Double-click the file named setup.ini to edit it with Notepad.
 * 4) Replace VSdotNET in INSTANCENAME=VSdotNET with the new instance name.
 * 5) From the File menu, click Save and exit Notepad.

To install MSDE

<ol> From the Start menu, choose Run.</li> Type C:\Program Files\Microsoft Visual Studio .NET\Setup\MSDE\ and click OK.</li> Double-click the file named setup.exe.

Wait for the MSDE to complete installation. Setup is complete when the Windows Installer dialog box disappears.

NOTE: If during Setup you see the message: &quot;Setup failed to configure the server&quot; see the following Microsoft Knowledge Base article:

309398 PRB: SQL Server 2000 installation fails with an &quot;SSL Security error :ConnectionOpen (SECDoClientHandshake)&quot; error message

</li></ol>

To start the SQL (MSDE) service
 * 1) From the Start menu, choose Run.
 * 2) Type NET START MSSQL$VSdotNET and click OK.

NOTE: If you installed MSDE with a different instance name, replace &quot;VSdotNET&quot; with the new name in the above command.

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 CD1 or DVD.

4.5 Installing Windows 2000 SP2 Symbols
Windows 2000 SP2 symbols are provided on Visual Studio .NET installation media for system administrators and other advanced users to diagnose application and computer failures. These files are only appropriate for Windows 2000 users.

To install the Windows 2000 SP2 Symbols

NOTE: The Windows Component Update step must be completed prior to installation of symbols. If you run this Setup before completing the Windows Component Update step, you will not install the symbols.
 * 1) Insert the Windows Component Update disk.

-or-

Insert the Visual Studio .NET DVD, and then open the WCU folder.
 * 1) Open the Win2kSP2\Symbols\ folder.
 * 2) Double-click sp2sym.exe and extract the files to a local folder.
 * 3) Open  \Support\Debug.
 * 4) Open DBG_SP.htm, and then click Install Service Pack 2 Symbols.

4.6 Uninstalling Visual Studio .NET
To uninstall Visual Studio .NET, use the Add/Remove Programs tool in Control Panel.

Uninstalling Windows Component Updates

Uninstalling Visual Studio .NET does not uninstall components installed by Windows Component Update. For components that offer individual uninstall, use the Add/Remove Programs tool in Control Panel.

Uninstalling system service packs

If you have not installed Windows NT 4.0 Service Pack 6a or Windows 2000 SP2 prior to installing Visual Studio .NET and you want to be able to uninstall the service package, you should manually install the service pack and enable the option to backup files for uninstall before you install Visual Studio .NET. Although Visual Studio .NET installs the appropriate service pack as part of its update of system components, the Visual Studio .NET installation does not create the uninstall directory.

Keywords: kbvs2005doesnotapply kbhowto kbvs2005swept kbide kbinfo kbsetup KB312779

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.