"Class not registered" error message when you try to create a Visual Studio Analyzer project (823238)
The information in this article applies to:
- 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
SYMPTOMSIn Visual Studio .NET, when you try to create a Visual
Studio Analyzer project, you may receive the following error message: Class not registered In Visual Studio .NET, when you
run the Visual Studio Analyzer Project Wizard, you may receive the following error message: Visual Studio Analyzer could not find any registered events
on ComputerName Note ComputerName is a placeholder for the
name of your computer. Additionally, in Step 2 of the Visual Studio
Analyzer Project Wizard, you may notice that the list of components is
empty. When you try to open an existing Visual
Studio Analyzer project in Visual Studio .NET, you may receive the following error messages in Solution
Explorer: ProjectName
(unavailable) The project file cannot be loaded. Note ProjectName is a placeholder for the
name of your existing project. CAUSEWhen you install Visual Studio .NET 2003 on a computer that
already has Visual Studio .NET 2002 installed, Visual Studio .NET 2003
overwrites the registry key that contains information about the version of
Visual Studio Analyzer that is installed with Visual Studio .NET 2002.
When you remove Visual Studio .NET 2002, Visual Studio .NET 2002 does
not verify whether Visual Studio .NET 2003 is also installed on your computer, and
the uninstaller removes the information that is contained in the registry key.
Therefore, after you remove Visual Studio .NET 2002, you may experience the
behavior that is discussed in the "Symptoms" section.
Note This behavior occurs when
you perform a side-by-side installation of Visual Studio .NET 2002 and Visual Studio .NET
2003, and then you remove either Visual Studio .NET 2002 or Visual Studio
.NET 2003. This behavior occurs regardless of the version of the product that you install first.RESOLUTIONTo resolve this problem for the scenario that is described in the
"More Information" section, repair your existing installation of Visual Studio
.NET 2003. To do this, follow these steps:
- Quit Visual Studio .NET 2003.
- Do the following, depending on your operating system:
- Microsoft Windows 2000
In Control Panel, double-click Add/Remove Programs. - Microsoft Windows XP or Microsoft Windows Server 2003
In Control Panel, click Add or
Remove Programs.
- In the Add or Remove Programs dialog box,
click your Visual Studio .NET 2003 installation. For example, if you have
installed the English version of Visual Studio .NET 2003 Enterprise Architect
Edition, click Microsoft Visual Studio .NET Enterprise Architect 2003
- English.
- Click Change/Remove.
- In the
Visual Studio .NET Setup dialog box, click Visual
Studio .NET.
- On the Visual Studio .NET Maintenance
Page, click Repair/Reinstall.
- When the repair is completed, click Done.
- In the Visual Studio .NET Setup dialog
box, click Exit.
- Create a new Visual Studio Analyzer project. To do this, follow these steps:
- Start Visual Studio .NET 2003.
- On the File menu, point to
New, and then click Project.
- Under Project Types,
expand Other Projects.
- Under Other Projects, click
Visual Studio Analyzer Projects.
- Under Templates, click
Analyzer Project, and then click OK.
- On the File menu, click Close
Solution.
- Use the Visual Studio Analyzer Project
Wizard to create a new Visual Studio Analyzer project. To do this, follow these steps:
- On the File menu, point to
New, and then click Project.
- Under Project Types, click
Visual Studio Analyzer Projects.
- Under Templates, click
Analyzer Wizard, and then click
OK.
- In Step 1 of the Visual Studio Analyzer Project
Wizard, click to select the name of your computer, and then click
Next.
- In Step 2 and Step 3 of the
Visual Studio Analyzer Project Wizard, click Next.
- In Step 4 of the
Visual Studio Analyzer Project Wizard, click Finish. A Visual Studio
Analyzer dialog box appears.
- Close the Visual Studio Analyzer dialog
box.
- On the File menu, click Close
Solution.
- On the File menu, point to
Open, and then click Project.
- In the Open Project dialog box, locate and
then click any existing Visual Studio Analyzer project. Click
Open.
The project opens without the
errors that appear in the "Symptoms" section.
STATUS This
behavior is by design.REFERENCESFor more information, visit the following Microsoft
Web sites:
Modification Type: | Minor | Last Reviewed: | 2/21/2006 |
---|
Keywords: | kbvs2005swept kbvs2005doesnotapply kbVSVisAnalyzer Kbsxs kbDeployment kbSoftwareDist kbsetup kberrmsg kbprb KB823238 kbAudDeveloper |
---|
|