RegClean Revisited

5 Aug 2010 10:48 PM

BeeJ

Now I have several Reg Clean programs and none of them find the
"orphaned" (missing) once registered items that are listed in
Project\References.
So, does the VB6 IDE store this list elsewhere?
In the registry?
How do I locate and delete those items?

5 Aug 2010 11:18 PM

Kevin Provance

"BeeJ" <nospam@nowhere.com> wrote in message
news:i3ff47$3jb$1@speranza.aioe.org...
: Now I have several Reg Clean programs and none of them find the
: "orphaned" (missing) once registered items that are listed in
: Project\References.
: So, does the VB6 IDE store this list elsewhere?
: In the registry?
: How do I locate and delete those items?

Fire up RegMon and look for yourself. That's what I would do.

6 Aug 2010 1:17 AM

BeeJ

Kevin Provance formulated on Thursday :

> "BeeJ" <nospam@nowhere.com> wrote in message
> news:i3ff47$3jb$1@speranza.aioe.org...
>> Now I have several Reg Clean programs and none of them find the
>> "orphaned" (missing) once registered items that are listed in
>> Project\References.
>> So, does the VB6 IDE store this list elsewhere?
>> In the registry?
>> How do I locate and delete those items?
>
> Fire up RegMon and look for yourself. That's what I would do.

RegMon no longer is available. Now is ProcMon.
And I do not see what that can do for me locating stuff that shows up
in References.

5 Aug 2010 11:47 PM

ralph

On Thu, 05 Aug 2010 15:48:38 -0700, BeeJ <nospam@nowhere.com> wrote:

>Now I have several Reg Clean programs and none of them find the
>"orphaned" (missing) once registered items that are listed in
>Project\References.
>So, does the VB6 IDE store this list elsewhere?
>In the registry?
>How do I locate and delete those items?
>

You can't do that with an outside tool.
(I hope I didn't give you that impression before. If I did it was
because I didn't realize you were asking for that kind of help.)

If something is marked "missing" then you have to either manually
change it to point to something valid or delete it. (Either through
the Reference menu item, or in the file.)

This is by design.

If you are constantly having this problem is probably because you are
not using the project and binary compatibility options.

It is useful to get the Interface (classes) worked out as soon as into
a project as you can. For the purpose of project/binary compatiblity
they don't need a full implementation. Just serve as placeholders as
stubbed out.

-ralph

6 Aug 2010 1:00 AM

BeeJ

ralph wrote on 8/5/2010 :
Show quoteHide quote

> On Thu, 05 Aug 2010 15:48:38 -0700, BeeJ <nospam@nowhere.com> wrote:
>
>> Now I have several Reg Clean programs and none of them find the
>> "orphaned" (missing) once registered items that are listed in
>> Project\References.
>> So, does the VB6 IDE store this list elsewhere?
>> In the registry?
>> How do I locate and delete those items?
>>
>
> You can't do that with an outside tool.
> (I hope I didn't give you that impression before. If I did it was
> because I didn't realize you were asking for that kind of help.)
>
> If something is marked "missing" then you have to either manually
> change it to point to something valid or delete it. (Either through
> the Reference menu item, or in the file.)
>
> This is by design.
>
> If you are constantly having this problem is probably because you are
> not using the project and binary compatibility options.
>
> It is useful to get the Interface (classes) worked out as soon as into
> a project as you can. For the purpose of project/binary compatiblity
> they don't need a full implementation. Just serve as placeholders as
> stubbed out.
>
> -ralph

The ones I see are ones that got registered then i forgot about them
and deleted the folders containing the files. Did that too many times.
I am now using a different folder structure so it won't (hopefully)
happen again. But I still would like to delete those cluttering
references.
How do I find the references?
I am afraid to use a tool like RegMon. I will probably blow up my PC.

6 Aug 2010 2:14 AM

Mayayana

| How do I find the references?
| I am afraid to use a tool like RegMon. I will probably blow up my PC.
|

Just don't light the fuse. :)

Seriously, though, Regmon just monitors access to
the Registry. What you want is something that
walks the HKCR\CLSID keys, checking all InProcServer32
and LocalServer32 subkeys to make sure their default
values point to a valid file. You might also check all
Typelib subkeys, which reference GUID keys under
HKCR\Typelib. As Kevin said before, it's really not
so farfetched to just write your own tool.

6 Aug 2010 1:19 AM

BeeJ

BeeJ has brought this to us :

> Now I have several Reg Clean programs and none of them find the "orphaned"
> (missing) once registered items that are listed in Project\References.
> So, does the VB6 IDE store this list elsewhere?
> In the registry?
> How do I locate and delete those items?

I used RegEdit to Find the References but it only finds the current and
active ones. The others that show up in References are not found in
the registry with Find. So does VB6 save these some place else?

6 Aug 2010 2:02 AM

ralph

On Thu, 05 Aug 2010 18:19:13 -0700, BeeJ <nospam@nowhere.com> wrote:

>BeeJ has brought this to us :
>> Now I have several Reg Clean programs and none of them find the "orphaned"
>> (missing) once registered items that are listed in Project\References.
>> So, does the VB6 IDE store this list elsewhere?
>> In the registry?
>> How do I locate and delete those items?
>
>I used RegEdit to Find the References but it only finds the current and
>active ones. The others that show up in References are not found in
>the registry with Find. So does VB6 save these some place else?
>

Yes, in the Project and Form files (for controls).

You can open those files with a text editor, and see what it is
looking for. But I'm still not sure what it is you expect to learn
from doing that. If a component is "missing" it is because the
Registry information no longer matches an existing component.

It sounds like you might be better off to just delete any "missing"
references. Make sure you have an existing component. Reregister it.
Then create a new reference.

-ralph