Registry entries are missing after you remove Visual Studio .NET 2003 from a computer that also has Visual Studio .NET 2002 installed (814698)

The information in this article applies to:

Microsoft .NET Framework 1.1
Microsoft .NET Framework 1.0
Microsoft Visual Studio .NET (2003), Professional Edition
Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
Microsoft Visual Studio .NET (2003), Academic Edition
Microsoft Visual Studio .NET (2002), Professional Edition
Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
Microsoft Visual Studio .NET (2002), Academic Edition

SYMPTOMS

If you install and then remove Microsoft Visual Studio .NET 2003 on a computer that has Visual Studio .NET 2002 already installed, you may notice that the following registry entries are missing:

The registry entry that contains information about the type library for Vdt70p.dll:
HKEY_CLASSES_ROOT\TypeLib\{0250A161-31AF-4FD5-8381-354894204930}
The registry entry that contains information about the type library for Vdt70.dll:
HKEY_CLASSES_ROOT\TypeLib\{C278AFDA-7859-4397-BFA2-66A9A0072483}

CAUSE

This problem occurs because these registry entries are removed automatically when you remove Visual Studio .NET 2003.

When you install Visual Studio .NET 2003 on a computer that has Visual Studio .NET 2002 already installed, the Vdt70p.dll file and the Vdt70.dll file are updated from version 7.0.9466.0 to the version that is included with Visual Studio .NET 2003 (for example, version 7.10.2346.0). The corresponding registry entries under the TypeLib registry key are also updated. However, these updated registry entries are removed when you remove Visual Studio .NET 2003.

RESOLUTION

To resolve this problem, repair Visual Studio .NET 2002. To do this, follow these steps:

Insert the Visual Studio .NET 2002 CD-ROM in the CD-ROM drive of your computer.
In the Visual Studio .NET Setup dialog box, click Visual Studio .NET.
On the Maintenance Page that appears, click Repair/Reinstall.
When the repair has completed, click Done, and then click Exit.

When the repair has complete, you can add references to Vdt70p.dll and Vdt70.dll.

STATUS

Microsoft has confirmed that this is a bug in Microsoft Visual Studio .NET 2003.

MORE INFORMATION

Steps to Reproduce the Behavior

Install Visual Studio .NET 2002.
On the same computer, install Visual Studio .NET 2003.
When the installation has completed, remove Visual Studio .NET 2003.
Click Start, and then click Run.
In the Open text box, type regedit, and then click OK.
Verify that the following registry entries are missing:
HKEY_CLASSES_ROOT\TypeLib\{0250A161-31AF-4FD5-8381-354894204930}
HKEY_CLASSES_ROOT\TypeLib\{C278AFDA-7859-4397-BFA2-66A9A0072483}

REFERENCES

For more information, visit the following Microsoft Web sites:

Adding and Removing Project References
http://msdn.microsoft.com/library/en-us/vsintro7/html/vxtskAddingRemovingProjectReferences.asp

Inside Distributed COM: Type Libraries and Language Integration
http://msdn.microsoft.com/library/en-us/dncomg/html/dcomtyplib.asp

Interface Definitions and Type Libraries
http://msdn.microsoft.com/library/en-us/midl/midl/interface_definitions_and_type_libraries.asp

Runtime Callable Wrapper
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconruntimecallablewrapper.asp

Installation and Setup
http://msdn.microsoft.com/library/en-us/vsintro7/html/vxoriInstallationSetup.asp

Registry
http://msdn.microsoft.com/library/en-us/sysinfo/base/registry.asp

Modification Type:	Minor	Last Reviewed:	2/4/2006
Keywords:	kbvs2005doesnotapply kbvs2005swept kbvs2002sp1sweep kberrmsg kbwizard kbWindowsForms kbui kbSetupMan kbRepair kbRegistry kbForms kbDLL kbDevStudio kbSysSettings kbinterop kbenv kbAppSetup kbsetup kbide kbCmnDlg kbPDWizard kbDeployment kbCOMInterop kbNameSpace kbBug KB814698 kbAudDeveloper