Should FEShlExt.dll be unregistered?

[therube]

Should FEShlExt.dll be (at the least) unregistered (if not removed altogether)?

Everything always crashes FEShlExt.dll


(Not that I'd think it likely to matter, in any manner , but if a user had the old version installed, & also had the current version installed... unregistering/removing [FEShlExt.dll] would nuke the old version's access to context-menu...)

[Administrator]

AllDup uses FEShlExt.dll if the context menu option "Context menu without Unicode support" is activated.

[therube]

But here you said, The FastExplorer files are from version 4.5.33 (or below) and not used anymore since 4.5.35. ?

And by "The FastExplorer files" you do mean, FEShlExt.dll?

Context menu without Unicode support

Where is that found?
Or is it only during the install, or does it only appear depending on ones OS configuration?

(I don't think I saw it during install, nor am I finding it otherwise, within the program?
I do see, Options | General -> Unicode-Text Support, but I take it that is different?)


(I'll note that the version I installed, which I happened to have on hand, was 4.5.38.
I do have ... [OK, now I really confused... ?]
Otherwise, I typically only use the Portable versions.)

I do have ... [OK, now I really confused... ?]

I [also] do have, on hand, 4.5.22, & if I install that version, then FEShlExt.dll turns up.

[Administrator]

This context menu option is available since v4.5.40. Please use the latest version of AllDup and check the version history.

[therube]

Tell me if I've got this right...

< = 4.5.33, uses FEShlExt.dll (for context menu)
> = 4.5.35, uses KuShellExtension64.dll [& FastExplorer*.ini] (for context menu)

That said ...

If a user has a < = 4.5.33 version installed,
& then updates to a later version (so >= 4.5.35),
FEShlExt.dll is no longer used, instead KuShellExtension64.dll is used.

That is all fine.

The issue that I was bringing up (& maybe not too clearly at that) is that when you update from < = 4.5.33 to a later version, FEShlExt.dll is left physically (is not uninstalled) & is also left registered.

I.e., FEShlExt.dll is not unregistered, & is not deleted (with an update to version > 4.5.33).

And my question is that should updating to > 4.5.33, at the least unregister FEShlExt.dll (given that theoretically it will no longer be used)?

[Administrator]

AllDup uses both DLL files depending on the selected context menu option.

[therube]

Please use the latest version of AllDup and check the version history.

Ah, I'm starting to get it.
(Sometimes I need to read better, & better understand what I'm reading.)

So the ability to use either the Unicode (KuShellExtension64.dll) or the older non-unicode (FEShlExt.dll) version only started with 4.5.44.
(And since I didn't have .44 or .50 [at the time] installers, what I was seeing [wasn't seeing] was not registering with me. Which leads back to the read better... .)

So one can choose, interactively at that, which version is used.

Similarly, Ku... uses config.xml & FES... uses FastExplorer.ini.
And their absence, or not, corresponds with the method chosen.
And lack altogether of both the .xml & .ini means that the 'Integrate AllDup...' is not selected at all.

[therube]

Is the actual 'Register' button (in Options | General | -> Integrate...) superfluous?

As in, simply enabling 'Integrate AllDup into the Windows Explorer context menu' is sufficient to get things working (without needing to specifically click the Register button).

Or does clicking Register actually do more?

[Administrator]

Is the actual 'Register' button (in Options | General | -> Integrate...) superfluous?

Yes, if AllDup's context menu is displayed in the Windows Explorer context menu...

Or does clicking Register actually do more?

No.