by Nicholas Forystek (14 Submissions)
Category: Windows System Services
Compatability: VB 6.0
Difficulty: Advanced
Originally Published: Sat 24th March 2018
Date Added: Tue 9th February 2021
Rating: 
(1 Votes)
Sometimes, and not likely, but you may wish you did not forfeit compile testing with a name that you really want to use for a project on a system you just got up and don’t want to refresh the OS install, a development system. So now the program ID or file name has multiple interfaces and/or class ID’s and they won’t act or behave properly for the one you have decided to go with for the development of the project design after testing. Also there is sometimes a issue where with ActiveX controls and modules, which embed, will reference on a particular interface to a module and it becomes invalid caught in limbo to anything attempted by another project’s references failing the latest due to a third or more reference to the component. Thus, this post and small program is nifty but it’s really just for developers where as the interfaces may be many but never went out on releases. What it does is what it states, cleans the registry (deletes) of traces of the search program ID entered. It removes in a hierarchy intuition not hard code checks in locations, seeking out all class ID references in conjunction to the program ID entered from class root to interface. Creates backup and a log during actual removal, it also uses another VBCode.com post for the registry API module.
VBcoders
