Help and Support
 

powered byLive Search

BUG: "Library not registered" error message when you start a new application project by using Visual C# .NET

Article ID:823244
Last Review:May 16, 2007
Revision:1.8
On This Page

SYMPTOMS

You have Visual Studio .NET 2002 or Visual Studio .NET 2003 installed on your computer. You create a setup project that includes Extensibility and VSLangProj assemblies, and then you install the setup project on your computer.

When you remove the setup project, and then create a new project by using Visual C# .NET, you receive the following error message:
Library not registered

Back to the top

CAUSE

This problem occurs because the setup project adds a dependency to the following files:
VSLangProj.dll
VsLangProj.tlb
Extensibility.dll
Extensibility.tlb
When you remove the setup project, the VSLangProj.tlb file and the Extensibility.tlb file are unregistered. However, Visual Basic .NET and Visual C# .NET use these TLB files. When you try to create a new application project, the project cannot find the Extensibility.tlb file and the VSLangProj.tlb file. Therefore, you receive the error message that is described in the "Symptoms" section.

Back to the top

WORKAROUND

To work around this problem, do one of the following:
Repair or re-install Visual Studio .NET 2002 or Visual Studio .NET 2003. To do this, follow these steps:
1.Quit Visual Studio .NET.
2.In Control Panel, double-click Add or Remove Programs.
3.Click Microsoft Visual Studio .NET, and then click Change/Remove.
4.In Microsoft Visual Studio .NET Setup, click Visual Studio .NET, and then click Repair/Reinstall.
-or-
Exclude the Extensibility assembly and the VSLangProj assembly from the setup project when you install the setup project on your computer.

Back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

Steps to reproduce the behavior

Note To reproduce this behavior, you must have Visual Studio .NET 2002 or Visual Studio .NET 2003 installed on your computer.
1.In Microsoft Visual Studio .NET, use Visual Basic .NET or Visual C# .NET to create a new Windows Application project. By default, Form1 is created.
2.Add a new reference to this project, and then build the project. To do this, follow these steps:
a. In Solution Explorer, right-click WindowsApplication1, and then click Add Reference.
b. Click the .NET tab, click extensibility. Hold down the CTRL key, and then click VSLangProj. Release the CTRL key, and then click Select. Click OK.
c. On the Build menu, click Build Solution.
3.Add another project to the project that you created in step 1. To do this, follow these steps:
a. On the File menu, point to Add Project, and then click New Project.
b. In the Add New Project dialog box, click Setup and Deployment Projects under Project Types, click Setup Project under Templates, and then click OK. By default, Setup1 is created.
c. In Solution Explorer, click Setup1.
d. On the Project menu, point to Add, and then click Project Output.
e. In the Add Project Output Group dialog box, click Primary output, and then click OK.
f. On the Build menu, click Build Setup1.
4.Install the project that you have created. To do this, follow these steps:
a. On the Project menu, click Install.
b. On the Welcome to the Setup1 page of the setup wizard, click Next.
c. On the Select Installation Folder page, type the location where you want to install the project in the Folder text box.
d. Click Next.
e. On the Confirm Installation page, click Next.
f. On the Installation Complete page, click Close.
5.On the Project menu in Visual Studio .NET, click Uninstall.
6.After the uninstall process is completed, quit Visual Studio .NET.
7.Start Visual Studio .NET 2002 and Visual Studio .NET 2003, and then use Visual C# .NET to create a new Windows Application project.

You receive the error message that is described in the "Symptoms" section of this article.

Note If you use Visual Basic .NET to start the new Windows Application project, you do not receive an error message and the application project starts as expected.

Back to the top

REFERENCES

For more information, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/19x10e5c(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/19x10e5c(vs.71).aspx)

Back to the top


APPLIES TO
Microsoft Visual Studio .NET 2003 Enterprise Architect
Microsoft Visual Studio .NET 2003 Enterprise Developer
Microsoft Visual Studio .NET 2003 Academic Edition
Microsoft Visual Studio .NET 2002 Professional Edition
Microsoft Visual Studio .NET 2002 Enterprise Architect
Microsoft Visual Studio .NET 2002 Enterprise Developer
Microsoft Visual Studio .NET 2002 Academic Edition
Microsoft Visual C# .NET 2003 Standard Edition
Microsoft Visual C# .NET 2002 Standard Edition

Back to the top

Keywords: 
kbvs2005doesnotapply kbvs2005swept kbvs2002sp1sweep kbpending kbsetup kbdll kbbug KB823244

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by E-mail, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.