interop for vb6 dll

We have created a VB6 dll that will need to be referenced in a .Net (VS 2010) project. Normally when I reference com dlls, such as Microsoft.Excel, I see an interop being created in the references. When I reference this dll, by browsing to it, the reference is created, but without the interop. Do I somehow need to create an interop? How do I do that?

Did you build the VB6 DLL as a COM component? I'm not fully sure why there are Interop* libraries for Office libraries (maybe they are wrappers around the new libraries), but if you exposed your VB6 as a COM component, then you should be able to use the library once you add the reference--no need to worry about an "Interop" piece.

Featured Post

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention. Check out this how-to article for more information.

Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …

I was working on a PowerPoint add-in the other day and a client asked me "can you implement a feature which processes a chart when it's pasted into a slide from another deck?". It got me wondering how to hook into built-in ribbon events in Office.

Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…

Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…