Forum Discussion
Sep 15, 2023
Notepad++ 8.5.7 and "ExplorerCommandHandler" used to register the Context Menu
A company complained to me about Notepad++ version 8.5.7 and packaging it into MSIX. It seems that the vendor changed how the native install registers their context menu. Rather than registering un...
TomPaul678
Oct 13, 2023Copper Contributor
I just came across this problem with appv 5.1. Updated the notepad version and the context menu is gone.
- Roger_WernliOct 30, 2023Copper Contributor
Here also context menu issues with App-V 5.1.
Notepad++ 7.8.5 works fine
Notepad++ 8.5.8 doesn't work:
Does someone know if there is a way to resolve it?
- Oct 30, 2023When repackaging for App-V, the only solution right now is as follows:
After installing/configuring the app, use the registry to modify the SHELL file association under "Classes\*" (there might be a ProgID involved, so if so look there -- I am going from memory here!)
Under the shell entry you'll find a value name of "ExplorerCommandHandler". You can remove everything under the "Shell" key, and then under that add a traditional Shell Integration (since the menu provided by the shell extension is the same every time), which is a key "Open" containing a key "Command" with a default value of the path to the Notepad++ exe file with "%1" as an argument.
See https://www.tmurgent.com/TmBlog/?p=3643 for more explanation.- Roger_WernliNov 20, 2023Copper Contributor
Hi Tim
Thanks and sorry for the late reply.
The "old" context menu does work but the icon is missing.
On the sequenzer the icon is shown and the parameter has has been added to the registry.
On a test client if i look outside of the Notepad++ virtual environment the icon parameter has not been published.
If i look inside of the Notepad++ virtual environment the icon parameter is available but the path has not been resolved.
I think the path should look like in the command key.
Any idea why this is happening?
kind regards