ProgID and VB 6 references dialog

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I have functionality that I have to be used with a legacy VB 6 application. A
assembly has been created that contains a class that implements an interface
with the neccessary methods. The ProgID attribute has been used, note code
example below:

<ProgId("TheName.Testing"), _
ClassInterface(ClassInterfaceType.None), _
Guid("5xxEC844C-xxxx-466d-AF6D-8D73DE080896")> _
Public Class TestCOM
Implements ITestCOM

In VB 6 References dialog, the namespace of the assembly that has been
exposed to COM is displayed rather then the ProgID. Is this the correct
behavior or am I missing something?

Thanks
.

Relevant Pages

  • Re: Pythons simplicity philosophy
    ... >> personally argued that reduceshould be removed from the language, ... from legacy import * ... easy to get this functionality with a commandline switch, ... day-to-day python-dev traffic, but I don't think anything's been ...
    (comp.lang.python)
  • Re: Accelerated legacy code
    ... I'm calling it "accelerated legacy code". ... TOO hard to check things across Browsers (although it is definitely extra ... are dozens of very good packages around that provide that functionality. ... business folks aren't usually technical, ...
    (comp.lang.cobol)
  • Re: Clarion legacy to ABC Classes... Why?
    ... The legacy procedural code can use objects, but is not based on them. ... As a result it's harder to extend the functionality. ... So the relation Manager object derives and extends the functionality of the file manager. ... Can the legacy templates be object orientated? ...
    (comp.lang.clarion)
  • Re: Accelerated legacy code
    ... I'm calling it "accelerated legacy code". ... TOO hard to check things across Browsers (although it is definitely extra ... capability in Dreamweaver for more than 5 years, ... are dozens of very good packages around that provide that functionality. ...
    (comp.lang.cobol)