Re: Multiple references to same component in reference dialog

On Jan 30, 1:41 pm, "Ken Halter"
<Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Steve" <sredm...@xxxxxxxxxx> wrote in message

news:1170181993.094750.93460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

How do I clean up the VB reference list? I am talking about the
dialog that is displayed when you click the Project>References...menu
in the VB IDE. I have several entries for components I evidently
compiled to several different locations (some of which no longer
exist) during development. On Win9x and Windows 2K I used to run the M
$ utility called RegClean. This utility does not work on XP.

Can anyone tell me how to clean up the registry of these invalid
entries?

Thanks
Steve

fwiw, I use RegClean on XP/SP2. There are similar utilities out there as
well. Those "extras" are caused by compiling an activex component without
setting up and maintaining Binary Compatibility. Their physical location on
the hard drive doesn't matter. The interface IDs do, which are regenerated
every time you compile, unless you're using Binary Compatibility...

Binary Compatibilityhttp://www.vbsight.com/BinaryComp.htm

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory -http://www.vbsight.com/Remembrance.htm

My expperience is that if I compile a project with or without binary
compatability it will be registered and an entry will be created in
the References dialog box. If I then delete the compiled file without
unregistering it, the entry will still be in the registry and in the
References dialog. This entry will be an orphaned entry in that it no
longer points to a valid file. Furthermore, since the file no longer
exists, you can not unregister it...hence there will be no way of
getting rid of the entry.

As I said in my original post I used to use RegClean to clean these
issues up but it is not working now. In an attempt to find out why it
is not working I found an article from M$ that states that the utility
does not work on XP.

.

Relevant Pages

  • Re: float to pointer coercion (cost 13)
    ... Do you compile two versions of the ... but it is given two entry ... but to the immediate-args entry point. ... ((DOUBLE-FLOAT DOUBLE-FLOAT) ...
    (comp.lang.lisp)
  • Re: HLA suggestions
    ... >> This is only true if you compile a PROGRAM. ... >> For more details on controlling the code that HLA generates. ... lex level:) as the "_HLAMain" entry point...and the linker response ...
    (alt.lang.asm)
  • Re: float to pointer coercion (cost 13)
    ... Do you compile two versions of the ... but to the immediate-args entry point. ... I didn't realize that Maclisp used that technique. ... > Or maybe it came from some contemporary hack in the "Franz Lisp", ...
    (comp.lang.lisp)
  • Re: Linux kernel 2.4 programming problem
    ... I create a new entry in arch/i386/kernel/entry.S ... compile i receive a problem like this ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Linux kernel 2.4 programming problem
    ... I read guide/articles like this ... All the articles say the same things, but the implementation of my new ... I create a new entry in arch/i386/kernel/entry.S ... compile i receive a problem like this ...
    (Linux-Kernel)