This document lists issues that concern installation, uninstall, repair, and other
setup procedures.
- Issues for all Visual Studio Express Products
- Visual C# Express
- Visual Basic Express
- Visual J# Express
- Visual C++ Express
- .NET Framework
- MSDN Express
- Visual Studio Integrated Development Environment
- Visual Web Developer Express
1. All Visual Studio Express Products
1.1. System Requirements
System Requirements for Installing Visual Studio Express 2005:
|
Processor |
Minimum:
- 600 megahertz (MHz) Pentium processor
Recommended:
- 1 gigahertz (GHz) Pentium processor
|
|
Operating System
|
Visual Studio Express can be installed on any of the following systems:
- Microsoft® Windows® 2000 Professional SP4
- Microsoft® Windows® 2000 Server SP4
- Microsoft® Windows® 2000 Advanced Server SP4
- Microsoft® Windows® 2000 Datacenter Server SP4
- Microsoft® Windows® XP Professional x64 Edition (WOW)
- Microsoft® Windows® XP Professional SP2
- Microsoft® Windows® XP Home Edition SP2
- Microsoft® Windows® XP Media Center Edition 2002 SP2
- Microsoft® Windows® XP Media Center Edition 2004 SP2
- Microsoft® Windows® XP Media Center Edition 2005
- Microsoft® Windows® XP Tablet PC Edition SP2
- Microsoft® Windows Server™ 2003, Standard Edition SP1
- Microsoft® Windows Server™ 2003, Enterprise Edition SP1
- Microsoft® Windows Server™ 2003, Datacenter Edition SP1
- Microsoft® Windows Server™ 2003, Web Edition SP1
- Microsoft® Windows Server™ 2003, Standard x64 Edition SP1 (WOW)
- Microsoft® Windows Server™ 2003, Enterprise x64 Edition SP1 (WOW)
- Microsoft® Windows Server™ 2003, Datacenter x64 Edition SP1 (WOW)
- Microsoft® Windows Server™ 2003 R2, Standard Edition
- Microsoft® Windows Server™ 2003 R2, Standard x64 Edition (WOW)
- Microsoft® Windows Server™ 2003 R2, Enterprise Edition
- Microsoft® Windows Server™ 2003 R2, Enterprise x64 Edition (WOW)
- Microsoft® Windows Server™ 2003 R2, Datacenter Edition
- Microsoft® Windows Server™ 2003 R2, Datacenter x64 Edition (WOW)
- Microsoft® Windows Vista™
Installation of Visual Studio 2005 on the Intel Itanium (IA64) is not supported.
|
|
RAM1
|
Minimum:
Recommended:
|
|
Hard Disk2
|
Up to 1.3 GB of available space may be required
|
|
CD or DVD Drive
|
Not required
|
|
Display
|
Minimum:
Recommended:
- 1024 x 768 High Color — 16-bit
|
|
Mouse
|
Microsoft mouse or compatible pointing device
|
1.1.1. Performance improvement
Performance has not been tuned for minimum system configurations. Increasing your
computer's RAM will improve its performance, especially when running multiple
applications, working with large projects, or doing enterprise-level development.
1.1.2. Installation drive
When you start the Express 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 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.
1.2. Upgrade from previous releases of Visual Studio 2005
For best results, install on a computer that has not had pre-release
versions of SQL 2005, Visual Studio 2005, or the .NET Framework 2.0 installed on
it.
If your computer has any of the pre-release versions on it, they must be removed
in the correct order BEFORE you begin installing the release version.
This process is not officially supported. More information on
the uninstall process.
- Go to the Control Panel and launch Add/Remove Programs.
- Remove all SQL Server 2005 products.
- Either run the uninstall tool, or follow the
manual uninstall instructions below.
- Install the Express Edition product or products you wish to use.
Most pre-release projects can be carried forward to the release version. Details
on any changes
needed for forward compatibility. If you have problems, take a look at
this link or report your specific issue on the
Visual Studio Express Forum.
Warning: This Auto-Uninstall Tool uninstalls ALL
pre-release Visual Studio 2005 products, including Visual Studio Express Editions,
Visual Studio Team System, Visual Studio Professional, and Visual Studio Standard.
Run autouninstall tool now
Manual Uninstall Instructions
If you decide to uninstall manually, without using the tool, be sure you uninstall
ALL Visual Studio 2005 product editions BEFORE you uninstall the .NET Framework
2.0.
- Go to the Control Panel and launch Add/Remove Programs
- Remove "MSDN Library for Visual Studio 2005 Beta"
- Remove "Microsoft SQL Server 2005 Express Edition"
- Remove "Microsoft SQL Server 2005 Tools Express Edition"
- Remove "Microsoft SQL Native Client"
- Remove "DMA Transport Update for VS 2005 Beta 2"
- Remove "Microsoft MSDN Express Library 2005 Beta"
- Remove all Microsoft Visual Studio Express Editions (such as Visual C# 2005 Express
Edition Beta)
- Remove "Microsoft Visual Studio 2005 Remote Debugger Light" (This step
is needed only if Visual Studio is installed on a 64-bit machine)
- Remove "Microsoft Visual J# .NET Redistributable 2.0 Beta Language Pack"
(This step is not needed if you have only the English Edition)
- Remove "Microsoft Visual J# .NET Redistributable Package 2.0 Beta"
- Ensure all Visual Studio 2005 products have been removed from your system
- Remove "Microsoft .NET Framework 2.0 Beta Language Pack" (This step is
not needed if you have only the English Edition)
- Remove "Microsoft .NET Framework 2.0 Beta"
Install the Express Edition or Editions you wish to use.
1.3. Product Installation
1.3.1 Installation of Visual Studio 2005 on the Intel Itanium (IA64) is not supported.
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.
1.3.2 SQL Express installation fails when pre-released SQL Express components are
not uninstalled
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:
- Remove "Microsoft SQL Server 2005 Express Edition"
- Remove "Microsoft SQL Server 2005 Tools Express Edition"
- Remove "Microsoft SQL Native Client"
You may ignore the Beta warning message about these components if they were uninstalled
previously.
1.3.3 Setup fails when installing from a mounted drive in a Virtual PC environment
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.
This is because the mounting software can only support 2.2 Gigabytes of data.
To resolve this issue
You can use a third-party DVD 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.
1.3.4 Disk space required for system drive may be up to 100 megabytes off.
The estimated disk space required to install the Express Editions may be 100 megabytes
off.
To resolve this issue
Free up an additional 100 megabytes on your machine to install the product.
1.3.5 Installing Visual Studio 2005 using the runas command fails.
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.
1.3.6 Installing Visual Studio 2005 from CD fails. A network installation is requested.
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.
- Create a folder (for example, VS2005) on the server.
- Create two subfolders, named VS, and MSDN within the top-level folder. For example:
VS2005\VS
VS2005\MSDN.
- Copy the contents of the Visual Studio 2005 CDs into the VS2005\VS folder. Select
Yes if prompted to overwrite any existing files.
- 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.
- Open Setup.ini in the VS subfolder using a text editor, such as Note:pad.
- In the [Documentation] section, change the line that starts with "DIR="
as follows:
[Documentation]
DIR=..\MSDN
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.
- In the VS subfolder, open the Setup folder.
- Open setup.sdb in a text editor, such as Note:pad, 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.
- 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.
- 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\
1.3.7 Installing any edition of Visual Studio 2005 from an installation path that
is longer 100 characters fails on Windows 2000.
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:
- From the Start menu, choose Run.
- Type cmd and then click OK.
- 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.
1.3.8 Installation path cannot accept non-ANSI characters on Japanese MUI OS.
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.
1.3.9 Antivirus applications that are configured to clean the Temp folder might
cause setup to fail
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.
1.3.10 Setup does not check disk space when auto-launching after selecting "reboot
later".
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.
1.3.11 Visual Studio file extensions are unregistered when Express edition is uninstalled.
If multiple Express Editions are installed on the same computer and then one is
uninstalled, the uninstall un-registers file extensions it has in common with the
other Express Editions. This disables double-clicking on file icons in Windows Explorer
to open a Visual Studio file type (.cs or .vb, for example).
To resolve this issue
There are two ways to work around this problem:
Go to the Windows Folder Options dialog box by using the Explorer's Tools | Folder
Options menu and reassociate the Visual Studio file-type extensions.
-- Or --
Uninstall and then reinstall the Express Editions, which will cause the file extensions
to be re-registered.
1.3.12 MSDN Express Library provides a specific version for each Express Edition.
MSDN Express Library provides versions specific to each of Visual Basic 2005 Express
Edition, Visual C++ 2005 Express Edition, Visual C# 2005 Express Edition, Visual
J# 2005 Express Edition, and Visual Web Developer 2005 Express Edition. The desired
set of documentation must be explicitly installed.
To resolve this issue
If you did not specify the desired documentation when you installed your Express
Edition, you can install it by using Add or Remove Programs in the Windows Control
Panel.
1.3.13 SQL Server Express is the only version of SQL Server that will work with
Express Editions other than Visual Web Developer Express Edition.
SQL Server Express is the only version of SQL Server that will work with Visual
Basic 2005 Express Edition, Visual C++ 2005 Express Edition, Visual C# 2005 Express
Edition, and Visual J# 2005 Express Edition.
To resolve this issue
If you did not specify SQL Server Express when you installed your Express Edition,
you can install it by using Add or Remove Programs in the Windows Control Panel.
1.3.14 Administrator Deployment is not supported for Express Editions.
Administrator deployment using SMS or Active Directory is not supported for Visual
Studio 2005 Express Editions. On a clean computer that is running Windows XP Professional,
if you run the utility to create an .ini file for deployment (using admin docs),
setup will launch but then hang after the feature selection screens.
To resolve this issue
There is no known resolution
1.3.15 Removing the .NET Framework breaks SQL Server 2005 and MSDN Express Library.
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 and MSDN Library only after removing all previous SQL Server 2005 components
and MSDN library components, as listed below.
To resolve this issue
- From the Control Panel, select Add or Remove Programs.
- Select SQL Server 2005 components and then click Remove to remove each component
below.
- Remove Remove "Microsoft SQL Server 2005 Express Edition
- Remove Remove "Microsoft SQL Server 2005 Tools Express Edition
- Remove Remove "Microsoft SQL server setup support files
- Remove Remove "Microsoft XML 6.0
- Remove Remove "Microsoft SQLXML 4.0
- Remove Remove "Microsoft SQL Native Client
- Remove Remove "Microsoft MSDN library
- Select .NET Framework 2.0 and click Remove.
- 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.
1.3.16 Ensuring that your applications execute on all versions of Visual Studio
2005.
The .NET Framework common language runtime (CLR) provides configuration options
that allow developers to specify which version of the CLR their application should
run against. However, this makes it difficult to test the applications against CLR
versions other than the one specified, because it requires manually reconfiguring
options in each application's config file.
To resolve this issue
Visual Studio 2005 provides a switch that, when turned on, forces all applications
executing on a given computer to run on the latest version of the runtime. This
switch overrides settings specified in the app.exe.config and host.config files,
which normally specify that the application run on either version 1.0 or version
1.1 of the CLR.
You can control this switch either by setting a registry key or by setting an environment
variable:
In the registry, activate the switch by using
HKLM\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR=dword:00000001
or deactivate it by using
HKLM\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR=dword:00000000
You can find a sample using the registry to activate/deactivate the switch poster
on
GotDotNet
-- Or --
Using an environment variable, activate the switch with COMPLUS_OnlyUseLatestCLR=1
or deactivate it with COMPLUS_OnlyUseLatestCLR=0
1.3.17 MSDN documentation for Express Editions of Visual Studio 2005 is not installed
to a user-specified folder, but instead to a default folder.
During installation of the MSDN documentation for Express Editions, you will be
prompted to select a destination folder for the documentation files. However, your
selected path is not respected and the documents are installed to this location:
C:\Program Files\Microsoft MSDN Quarterly\NETDOCS\V20.
To resolve this issue
There is no known resolution.
1.3.18 Under some conditions, uninstalling Visual Studio .NET 2003 will corrupt
your installation of Visual Studio 2005.
If Visual Studio 2005 is installed and then Visual Studio .NET 2003 is installed
on the same computer, uninstalling Visual Studio .NET 2003 will corrupt your installation
of Visual Studio 2005.
To resolve this issue
You must rerun Visual Studio 2005 setup from the CD and select the Repair/Reinstall
option.
1.3.19 Installation appears to hang when installing MSDN Express.
During an installation, the user may be prompted to reboot after certain components
are installed. After a reboot, installation should continue. However, when the installer
is trying to install MSDN Express after a reboot, the progress bar looks full and
the product is marked as installed even though setup has not yet completed and the
product is not fully installed. This condition makes it look like setup is hung
even though MSDN Express is being installed in the background.
To resolve this issue
Wait about 10 minutes for MSDN Express install to complete. The progress bar will
not change during that time.
1.3.20 After being uninstalled, SQL Server Express requires a reboot before it can
be reinstalled.
When all SQL Server Express components are uninstalled, and then SQL Server Express
is reinstalled using 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, reboot the computer before reinstalling SQL Server Express.
1.3.21 Launching Maintenance Mode from Add or Remove Program can take several minutes
and might give the appearance that setup has failed.
If you have other processes running when you launch Maintenance Mode, such as virus
scanning software, these processes can slow setup considerably and give the appearance
that setup has failed
To resolve this issue
Setup has not failed. Wait until it is finished or close other processes and try
again.
1.3.22 Download failure when downloading and installing an Express SKU.
The download and installation of an Express SKU will intermittently fail due to
the unreliability of the internet.
To resolve this issue
Visit Troubleshoot_Guide.htm on your CD or temp directory and rerun the bootstrapper
from the website and try the download again.
1.3.23 During the Express Installation, an Extracting Files dialog may appear for
2 to 3 minutes without showing any progress.
When extracting SQL Server Express, the dialog comes up due to a known issue with
the compression technology. The dialog does not show any progress but the installation
is still processing in the background.
To resolve this issue
Wait 2 to 3 minutes for the dialog to disappear.
1.3.24 Reboot is required after uninstalling SQL Server Express in order to successfilly
reinstall SQL Server Express.
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.
1.3.25 Visual Studio Class Designer Package load failure in Visual Studio 2005 after
beta 2 uninstall.
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
- From a cmd prompt, run del %windir%\assembly\GAC_MSIL\Microsoft.VisualStudio. EnterpriseTools.ClassDesigner\
8.0.0.0__b03f5f7f11d50a3a\ Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll
- From a cmd prompt, run del %windir%\assembly\GAC_MSIL\Microsoft.VisualStudio. EnterpriseTools.SdmDesigners\
8.0.0.0__b03f5f7f11d50a3a\ Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll
- 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
- 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
- From a cmd prompt, run %programfiles%\Microsoft Visual Studio 8\SDK\v2.0\bin\gacutil.exe
/if Microsoft.VisualStudio.EnterpriseTools.SdmDesigners.dll
- From a cmd prompt, run %programfiles%\Microsoft Visual Studio 8\SDK\v2.0\bin\gacutil.exe
/if Microsoft.VisualStudio.EnterpriseTools.ClassDesigner.dll
1.3.26 Using a third party tool to extract the ISO file fails.
The default setting for many third party tools does not handle long file names.
Some tools extract using the 8.3 file convention. Visual Studio 2005 setup requires
the files to be in their long filename format or else setup will fail.
To resolve this issue
Set the tool to handle long file names. This feature can usually be found in the
Advanced settings. If you can not find the setting, please refer to the ISO extraction
tool help documentation or contact the software vendor for assistance.
1.3.27 SQL Express fails when trying to install to a compressed folder.
Microsoft SQL Express cannot install to a compressed folder.
To resolve this issue
Either uncompress the folder or install to a different location.
2. Visual C# Express
2.1. Product Installation
2.1.1 Running a Bootstrapper on a Russian Operating System renders some characters
incorrectly.
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:
- Open the setup.xml file at [.NET SDK Install Dir]\Bootstrapper\Engine\ru\seup.xml
- Go to the bottom of the file and edit the CharSet Element's value. Change it
from 0 to 204
- Save the file.
- Rebuild / Republish your application
3. Visual Basic Express
3.1. Product Installation
3.1.1 Running a Bootstrapper on a Russian Operating System renders some characters
incorrectly.
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:
- Open the setup.xml file at [.NET SDK Install Dir]\Bootstrapper\Engine\ru\seup.xml
- Go to the bottom of the file and edit the CharSet Element's value. Change it
from 0 to 204
- Save the file.
- Rebuild / Republish your application
4. Visual J# Express
4.1. Product Installation
4.1.1 v1.1 VJ# redist does not install on a IA64 machine with v2.0 installed.
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. The problem
is that the wrong CharSet value is used.
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
4.1.2 Running a Bootstrapper on a Russian Operating System renders some characters
incorrectly.
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:
- Open the setup.xml file at [.NET SDK Install Dir]\Bootstrapper\Engine\ru\seup.xml
- Go to the bottom of the file and edit the CharSet Element's value. Change it
from 0 to 204
- Save the file.
- Rebuild / Republish your application
5. Visual C++ Express
5.1. Product Installation
5.1.1 C++ Tools for Itanium Setup Location for Itanium Redistributables
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 2005 Team
System products).
To resolve this issue
You can find the Itanium redistributables in the Microsoft Visual Studio 2005\VC\Redist\x86
folder.
6. .NET Framework
6.1. Product Installation
6.1.1 Installing SDK hangs at "setup is configuring the install…”.
Installation hangs for 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.
6.1.2 x64 .NET Framework Language Pack 2.0 ProductVersion says 1.1.##### instead
of 2.0.#####
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.
6.1.3 Installing Windows Server 2003, followed by the .NET Framework 2.0, and then
upgrading to Windows Server 2003 SP1 using a full CD, breaks .NET Framework 2.0
applications.
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.
- From the Control Panel, select Add or Remove Programs.
- Select Microsoft .NET Framework 2.0.
- Click Change/Remove.
- When the dialog box appears, select Repair and click Next.
- If prompted to do so, reboot the computer.
6.1.4 Installing on 64-bit OS when IIS 6 is in WoW64 mode will disable ASP.NET 1.1
in IIS.
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.
- Start Internet Information Services Manager (inetmgr.exe)
- Expand the local computer node and click on Web Sites node.
- From the Action menu, select Properties.
- In the Web Site Properties dialog box, select the ISAPI Filters tab.
- In the list of filters, select the ASP.NET 2.0 filter and click the Remove
button.
- Click the Add button and enter the following:
Filter Name: ASP.NET_ 1.1.4322
Executable: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_filter.dll
- Click OK.
- Under the Local Computer node, click on the Web Service Extensions node
- Under Tasks, click on Add a new Web Service Extension
- In the New Web Service Extension dialog box, enter the following:
Extension Name: ASP.NET v1.1.4322
For Required files, click Add... and enter: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
Check Set Extension status to Allowed.
Click OK.
6.1.5 x64 netfx SDK JPN has ProductVersion = 1.1.##### instead of 2.0.#####
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.
7. MSDN Express
7.1. Product Installation
7.1.1 Help Documentation Missing After Uninstalling the MSDN Express Library or
the .NET Framework
In certain uninstall scenarios, Windows Forms Help documentation will disappear.
The problem occurs when the product that was installed last, MSDN Express Library
or the .NET Framework, is subsequently uninstalled. The uninstall of the product
unplugs the documentation from the Help system.
Scenario 1 – Uninstalling the .NET Framework
The MSDN Express Library is installed first, followed by the .NET Framework. If
the .NET Framework is then uninstalled, the Windows Forms Help documentation will
not appear when viewing the MSDN Express Library.
Scenario 2 – Uninstalling the MSDN Express Library
The .NET Framework is installed first, followed by the MSDN Express Library. If
the MSDN Express Library is uninstalled, the Windows Forms Help documentation will
not appear when viewing the .NET Framework Help.
To resolve this issue
Choose the repair option that better matches your scenario:
.NET Framework uninstalled and the MSDN Express Library still installed. Run a repair
of the MSDN Express Library using the following steps:
- On the Start menu, open the Control Panel.
- In the control panel, double-click Add or Remove Programs.
- Select Microsoft MSDN 2005 Express Edition.
- Click the Change/Remove button.
- Select Repair.
- Click Next.
Once the repair has finished, the MSDN Express Library will once again contain the
Windows Forms Help documentation.
MSDN Express Library uninstalled and the .NET Framework is still installed. Run
a repair of the .NET Framework using the following steps:
- On the Start menu, open the Control Panel.
- In the control panel, double-click Add or Remove Programs.
- Select Microsoft .NET Framework 2.0.
- Click the Change/Remove button.
- Select Repair.
- Click Next.
Once the repair has finished, the .NET Framework will once again contain the Windows
Forms Help documentation.
8. Visual Studio Integrated Development Environment
8.1. Product Installation
There are no setup issues at this time.
9. Visual Web Developer Express
9.1. Product Installation
There are no setup issues at this time.