0

BrowserPlus update leaves behind redundant registry entries

Hi,

It looks like the CLSID of BrowserPlus DLLs change with every minor update. I'm not familiar with how CLSID management is supposed to be done, but I've noticed that while the old files are automatically deleted, their corresponding entry in the Windows registry remains.

Is this fixable? (i.e. Can BrowserPlus clean up after itself in the registry during an update?)

by
3 Replies
  • QUOTE (Jeremy @ May 6 2010, 08:06 AM) <{POST_SNAPBACK}>
    Hi,

    It looks like the CLSID of BrowserPlus DLLs change with every minor update. I'm not familiar with how CLSID management is supposed to be done, but I've noticed that while the old files are automatically deleted, their corresponding entry in the Windows registry remains.

    Is this fixable? (i.e. Can BrowserPlus clean up after itself in the registry during an update?)


    Yikes. As I recall, it's supposed to cleanup old registry entries. I'll file a bug for it and we'll get it fixed.

    -- gordon
    0
  • QUOTE (Gordon @ May 6 2010, 12:51 PM) <{POST_SNAPBACK}>
    Yikes. As I recall, it's supposed to cleanup old registry entries. I'll file a bug for it and we'll get it fixed.

    -- gordon


    Fixed (http://bugs.browserplus.org/show_bug.cgi?id=180). When the update containing this fix occurs, it will also remove the cruft that we left behind on previous updates.

    -- gordon
    0
  • Great work! :)
    0
This forum is locked.

Recent Posts

in Support & General Questions