This document contains notes for installing Visual Studio .NET 2003.
For the latest installation notes, see the online Visual Studio .NET 2003 Readme at http://go.microsoft.com/fwlink/?linkid=8861.
For known product issues, see http://go.microsoft.com/fwlink/?linkid=8793.
The End-User License Agreement (EULA.txt) for Visual Studio .NET 2003 is available for reference on CD1 in the Setup folder.
Note All procedures described in this readme are based on Microsoft® Windows® 2000. Modify the steps that interface with the operating system if you are using a different version of Windows.
In addition to this Visual Studio .NET 2003 product readme, Visual Studio .NET 2003 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.
| Content Name | File Name | Location |
|---|---|---|
| Microsoft Visual Studio .NET 2003 Prerequisites | Moreinfo.htm | In the Help directory of the Visual Studio .NET 2003 Prerequisites CD or in the wcu\Help directory of the DVD |
| Microsoft Visual Studio .NET 2003 Setup Administrator Mode Readme | Adminreadme.htm | In the Setup directory of the Visual Studio .NET 2003 CD1 |
| Microsoft .NET Framework SDK Readme | Knownissues.htm | http://go.microsoft.com/fwlink/?linkid=8862 |
| VSIP SDK | Readme.htm | VSIP SDK CD in the root directory |
| Duwamish 7.0 Visual Basic sample | Readme.htm | CD2\Program Files\Microsoft Visual Studio .NET 2003\Enterprise Samples\Duwamish 7.0 VB |
| Duwamish 7.0 C# sample | Readme.htm | CD2\Program Files\Microsoft Visual Studio .NET 2003\Enterprise Samples\Duwamish 7.0 CS |
| Fitch and Mather 7.0 sample | ReadMe.html | CD2\Program Files\Microsoft Visual Studio .NET 2003\Enterprise Samples\FMStocks7 |
| Student Tools | Readme.htm | Student Tools CD in the root directory |
| Faculty Tools | Readme.htm | Faculty Tools CD in the root directory |
| Microsoft SQL Server™ 2000 for Windows® CE Edition 2.0 | KB article — Q330971 | http://go.microsoft.com/fwlink/?LinkID=10614 |
The MSDN Library, which is designed to be used with Visual Studio .NET 2003, provides a broad range of help and documentation for Visual Studio .NET 2003 and other Microsoft technologies. During setup of Visual Studio .NET 2003, or at any other time, you can choose to install and integrate a later version of the MSDN Library than the version that is included with Visual Studio .NET 2003. The April 2003 or later versions of the MSDN Library can be integrated with Visual Studio .NET 2003. Earlier versions, such as January 2003, cannot be integrated with Visual Studio .NET 2003 and do not contain documentation for Visual Studio .NET 2003.
The tables below list requirements for different installation options of Visual Studio .NET 2003. The Notes identified here apply to both tables.
| Processor | 450 megahertz (MHz) Pentium II-class processor 600 MHz Pentium III-class processor recommended |
|||
| Operating System |
Visual Studio .NET 2003 can be installed on any of the following systems:
Applications can be deployed to the following systems2, 3:
|
|||
| Memory4 |
Visual Studio .NET 2003 minimum RAM requirements:
|
|||
| Hard Disk5 |
Visual Studio .NET 2003 disk space requirements:
|
|||
| Drive | CD-ROM or DVD-ROM drive is required for CD versions. DVD-ROM drive is required for DVD versions. |
|||
| Display | Super VGA (1024x768) or higher resolution display with 256 colors | |||
| Mouse | Microsoft mouse or compatible pointing device | |||
| Internet Connectivity | Visual Studio .NET 2003 Trial Edition requires Internet connectivity for mandatory online registration. Visual Studio .NET 2003 Academic Edition requires registration, which may be completed online. |
|||
| Processor | 450 megahertz (MHz) Pentium II-class processor 600 MHz Pentium III-class processor recommended |
|||
| Operating System |
Standard Editions can be installed on any of the following systems:
Applications can be deployed to the following systems2, 3:
|
|||
| Memory4 |
Minimum RAM requirements:
|
|||
| Hard Disk5 |
Disk space requirements:
|
|||
| Drive | CD-ROM or DVD-ROM drive is required for CD versions. DVD-ROM drive is required for DVD versions. |
|||
| Display | Super VGA (1024x768) or higher resolution display with 256 colors | |||
| Mouse | Microsoft mouse or compatible pointing device | |||
Both Visual Studio .NET 2003 and Visual Studio 6.0 can be installed on the same computer and run at the same time. For more information, see "Upgrading Applications", available in the MSDN Library.
Both Visual Studio .NET 2002 and Visual Studio .NET 2003 can be installed on the same computer and run at the same time.
For the latest installation instructions for Visual Studio .NET 2003, see http://go.microsoft.com/fwlink/?LinkId=8861.
Important If you have previously installed prerelease versions of the following products on your computer, you must uninstall those versions before installing Visual Studio .NET 2003:
Note For optimal installation of Visual Studio .NET 2003, you may need to reformat your computer if you previously installed the prerelease versions of the products listed above.
To uninstall prerelease versions of most programs
Note Instructions for uninstalling Visual Studio 7.0 PDC Technology Preview follow this procedure.
The following table provides instructions for the various prerelease versions.
| Prerelease Program | To uninstall |
|---|---|
Microsoft Visual Studio .NET 2003
Important See Note below table for additional procedures. |
|
|
|
| Smart Device Extensions Beta 1 |
|
| Visual Studio .NET 2002 Beta 2 or later |
|
| Visual Studio .NET Beta 1 |
|
1language is the specific language of the pack, for example, Japanese.
Note After uninstalling Visual Studio .NET 2003 Beta 1 and MSDN Library for Visual Studio .NET 2003 Beta 1, using the following procedure to delete the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\SxS\VS7:
- From the Start menu, click Run, type regedit, and then click OK.
- In the Registry Editor, expand the hive HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Studio\SxS.
- Right-click the VS7 key and click Delete in the shortcut menu.
- In the Confirm Key Delete dialog box, click Yes to delete the registry key.
To uninstall Visual Studio 7.0 PDC Technology Preview
msiexec.exe /x {33334F07-0C6B-11D3-A51D-00A0C9231BA1} NOVSUI=1
Select Yes to remove Visual Studio .NET PDC Technology Preview.
msiexec.exe /x {62EDCF3C-69F4-11D3-A521-00A0C9231BA1}
Select Yes to remove the Prerelease Bootstrap for Visual Studio .NET PDC Technology Preview.
The version of Visual Studio Analyzer shipping with Visual Studio .NET 2003 Enterprise Developer and Visual Studio .NET 2003 Enterprise Architect editions is not compatible with Visual Studio Analyzer 6.0.
If you are installing Visual Studio Analyzer that is included with the Visual Studio .NET 2003 Enterprise Developer or Visual Studio .NET 2003 Enterprise Architect on a computer that has Visual Studio Analyzer 6.0 installed, uninstall Visual Studio Analyzer 6.0 before installing Visual Studio .NET 2003.
If you have mistakenly installed both versions on the same computer, you cannot 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
To repair Visual Studio Analyzer 6.0 after uninstalling Visual Studio Analyzer
RegisterAnalyzerv7.bat
VSAReg.exe
Due to the nature of Visual Studio Analyzer, a particular machine may have only one version registered at a time. If you install Visual Studio .NET 2002 and its accompanying version of Visual Studio Analyzer on a machine and subsequently install Visual Studio .NET 2003 and its accompanying version of Visual Studio Analyzer on the same machine, you collect events from the version that was installed last.
To resolve this issue
Visual Studio .NET 2003 supports IPv6 on computers running Windows Server 2003 and Windows XP with a minimum of Service Pack 1.
On computers running Windows XP, you must install Windows XP Service Pack 1 before installing Visual Studio .NET 2003 if your projects rely on IPv6. In IPv6 scenarios, critical functions, such as opening and creating Visual Studio .NET projects, may fail if the service pack is not installed. If your projects do not rely on IPv6, installation of the service pack is not required.
If you have installed Visual Studio .NET 2003 before installing Windows XP Service Pack 1 and your projects rely on IPv6, see the KB article at http://go.microsoft.com/fwlink/?LinkId=11968.
Windows XP Service Packs are available at http://www.microsoft.com/windowsxp/pro/downloads/default.asp.
For additional information about enabling IPv6 for Visual Studio .NET 2003, read the file named IPv6.htm in the Setup directory of Visual Studio .NET 2003 CD1.
To install Visual Studio .NET 2003
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.
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
VS2003\PRE
VS2003\VS
VS2003\MSDN.
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.
"DIR=" as follows:
[Baseline]
DIR=..\PRE
FileName=setup.exe
"DIR=" as follows:
[Documentation]
DIR=..\MSDN
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.
[Product Key]
XXXXXXXXXXXXXXXXXXXXXXXXX
Note XXXXXXXXXXXXXXXXXXXXXXXXX is the 25 digit product key, entered without dashes, found on the CD packaging.
Note Completing this step enables pre-populating the product key for the user.
\\[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.
To work with Web applications in Visual Studio .NET 2003, your development computer and Web server must be properly configured.
Following are the operating system requirements for working with Web Forms and XML Web services in Visual Studio .NET 2003:
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
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 2003 installation.
Important debugging information
Visual Studio .NET 2003 does not include Microsoft SQL Server Desktop Engine (MSDE). To download MSDE, go to http://go.microsoft.com/fwlink/?linkid=13962.
Caution If you plan on installing Application Center 2000, you must install Application Center 2000 before installing MSDE.
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.
To uninstall Visual Studio .NET 2003, use the Add/Remove Programs Control Panel.
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.
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:
"Setup cannot find the original installation source location at <path to original install point>. Please check your drives and ensure setup can be found at that location."
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.
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.
Important Visual Studio .NET 2003 cannot be shared over a network using a shared CD-ROM drive. For information about installing Visual Studio .NET 2003 from a network share, see Facilitating Setup over a Network in this readme.
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.
This error may occur if you run setup with less than 900 MB of free space on your system drive.
To resolve this issue
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.
Note You must be logged on as administrator to the local computer to change registry size.
To change the maximum size of the computer's registry
If you upgrade your operating system after installing the .NET Framework, you must repair the .NET Framework.
To repair the .NET Framework
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
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
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:
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.
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
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.
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.
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
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.
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"
Note To run the MOF compiler, you need administrative privileges.
To resolve this issue
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.
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
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.
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
As an alternative, you can skip these steps, insert the MSDN CD included with Visual Studio .NET 2003, and run MSDN setup.
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
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
The Visual Studio integrated development environment (IDE) is part of the installation of several product editions, which are categorized according to the following list.
Visual C# .NET 2003 Standard
Visual C++ .NET 2003 Standard
Visual J# . NET 2003 Standard
Visual Studio .NET 2003 Academic
Visual Studio .NET 2003 Professional
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:
-or-
Although both options work, the second option requires more disk space.
Note The license for Visual Studio .NET 2003 Trial Edition expires in 60 days. Consequently, if you install Visual Studio .NET 2003 Trial Edition by selecting the second option, the IDE for neither installed product is accessible after the license expires. To start the other product, for example Visual Basic .NET 2003, you must uninstall Visual Studio .NET 2003 Trial Edition.
This message displays when a network error occurs during setup.
To resolve this issue
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
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.
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:
To resolve this issue
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
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.
Note For an OEM version of the operating system, copy files from the installation CD to a local destination:
- 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.
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
To uninstall Visual J# .NET Redistributable Package
To reinstall Visual J# .NET Redistributable Package
<DVD Drive>:\wcu\JSharpRedistCore\vjsredist.exe
-or-
<CD Drive>:\JSharpRedistCode\vjsredist.exe.
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
-or-
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
For a list of the changes and additions to the class library for the .NET Framework version 1.1, see http://go.microsoft.com/fwlink/?LinkId=8437.
For the latest security information, check the .NET Framework Security Web site at http://go.microsoft.com/fwlink/?LinkId=5588.
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.
Visit http://go.microsoft.com/fwlink/?LinkId=5201 for information on deploying the .NET Framework with your application.
For Visual Studio .NET 2003 known issues, see Visual Studio .NET 2003 Known Issues.
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.