Visual Studio .NET Analyzer tool may not work correctly after you repair it (814719)
The information in this article applies to:
- 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
SYMPTOMSIf you remove Microsoft Visual Studio .NET 2002 on a
computer that has Microsoft Visual Studio .NET 2003 already installed, the
Visual Studio Analyzer tool may not work correctly. After you run the
Registeranalyzerv7.bat file to repair the tool, Visual Studio Analyzer still
may not work correctly.CAUSEThis problem occurs because some files that the Visual
Studio .NET 2003 version of Visual Studio Analyzer uses become corrupted when
you remove Visual Studio .NET 2002.WORKAROUNDTo work around this problem, you must manually register the
default ProfDefV7.dll file. To do this, follow these steps:
- Click Start, and then click
Run.
- In the Run dialog box, type the following
command in the Open text box
Regsvr32 "Root\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\Analyzer\Bridges\WMI\ProfDefV7.dll" where Root is the root folder where
Visual Studio .NET 2003 is installed. - Click OK to register the DLL.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.REFERENCESFor more information, visit the following Microsoft
Developer Network (MSDN) Web site:
Modification Type: | Minor | Last Reviewed: | 3/6/2006 |
---|
Keywords: | kbvs2005swept kbvs2005doesnotapply kbvs2002sp1sweep kbpending kbVSVisAnalyzer kbDLL kbbug KB814719 kbAudDeveloper |
---|
|