Completely unregistering a component

I know this isn't directly VB related but since it appears that Visual Basic
is responsible I am hoping that someone has had similar problems.

We often have problems when another developer modifies a component (ocx or
dll) and then that item is checked out of Source Safe onto another computer.
If the interface has changed, the developer will need to reregister the
component. Unfortuately this often doesn't do the trick. Some times, it is
necessary to unregister the component and then reregister it.

Thus my questions.
Regsvr32 /u doesn't remove everything. It leaves references within typelib
and clsid keys. Is there a way to easily remove all of this information. We
are presently removing this information manually by searching the registry
for the filename.

Ideas? Procedures to prevent this to begin with?

Not sure what you want....
but might be this will help...
http://www.vbaccelerator.com/home/V...ry_Registration
_Utility/article.asp

--
playwin


"Glenn Welker" <Glenn Welker@discussions.microsoft.com> wrote in message
news:9C0852D5-65AB-4195-BEBF-C61C2DE62359@microsoft.com...
> I know this isn't directly VB related but since it appears that Visual
Basic
> is responsible I am hoping that someone has had similar problems.
>
> We often have problems when another developer modifies a component
(ocx or
> dll) and then that item is checked out of Source Safe onto another
computer.
> If the interface has changed, the developer will need to reregister
the
> component. Unfortuately this often doesn't do the trick. Some times,
it is
> necessary to unregister the component and then reregister it.
>
> Thus my questions.
> Regsvr32 /u doesn't remove everything. It leaves references within
typelib
> and clsid keys. Is there a way to easily remove all of this
information. We
> are presently removing this information manually by searching the
registry
> for the filename.
>
> Ideas? Procedures to prevent this to begin with?

"Glenn Welker" <Glenn Welker@discussions.microsoft.com> wrote in message
news:9C0852D5-65AB-4195-BEBF-C61C2DE62359@microsoft.com...
> We often have problems when another developer modifies a
> component (ocx or dll) and then that item is checked out of Source
> Safe onto another computer.  If the interface has changed, the
> developer will need to reregister the component.

If the Interface changes, then the DLL or OCX will contain different
GUID's, Interface ID's etc., etc.  In order to obliterate the previous
values from machines, you have to /unregister/ the previous version,
then register the new one.  Simply registering the new ones "over the
top" leaves all of old rubbish lying around.

However, for a DLL that's /only/ if the Interface changes - internal
code changes /shouldn't/ require this.
The same /ought/ to be true of OCX's but, in my experience, these
change their internal ID's almost at random whenever you build them.
(One reason why I abandoned OCX's many moons ago).

Of course, the only way to be /absoletely/ certain is

format c:         ;-)

HTH,
Phill  W.

Microsoft had an application called something like RegClean hidden on (it
might have been Windows 98) Windows disk. Or I might have downloaded from MS
Site.
Sorry I can't be more helpful

On Fri, 29 Apr 2005 11:55:39 +0000 (UTC), "Stuart Nathan"
<Stuart.Nathan@btopenworld.com> wrote:

>Microsoft had an application called something like RegClean hidden on (it
>might have been Windows 98) Windows disk. Or I might have downloaded from M
S
>Site.
>Sorry I can't be more helpful

Hmm.. my RegClean link to the MS site is no longer valid

Someone recommended this: http://www.jv16.org/

Searching MSDN for RegClean ...
http://search.microsoft.com/search/...1
&swc=0

<snip>
MORE INFORMATION
The RegClean utility is no longer supported and has been removed from
all Microsoft download sites.
</snip>

If using /anything/ then image your disk(s) first

"J French" <erewhon@nowhere.uk> wrote in message
news:42722b52.11300956@news.btclick.com...
> On Fri, 29 Apr 2005 11:55:39 +0000 (UTC), "Stuart Nathan"
> <Stuart.Nathan@btopenworld.com> wrote:
>
>
> Hmm.. my RegClean link to the MS site is no longer valid
>

This link to regclean should still work....
http://groups.google.co.uk/groups?s...>
utput=gplain

...and, if you want a 3rd party solution, I recommend....

System Mechanic 5
http://www.iolo.com/sm/5/index.cfm

...I've had great luck with it and it's much, much more than a simple
"RegClean" utility.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Sign up now to help keep VB support alive - http://classicvb.org/petition
Please keep all discussions in the groups..