PrimalScript • Re: After PrimalScript 2024 upgrade, Edit in PrimalScript did not work

Problem is that HKEY_LOCAL_MACHINE\SOFTWARE\Classes\textfile\shell\open\command is not a key we set. It does not even exit on any of my machines here.
Are you certain you have the root node correct?

SendToPS should only be referenced here:
HKEY_CLASSES_ROOT\SystemFileAssociations\text\shell\Edit with PrimalScript\command
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\text\shell\Edit with PrimalScript\command
Possibly here through user action:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ps1\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.txt\OpenWithList

If you have a remnant from a very old PrimalScript version, it could be that
HKEY_CLASSES_ROOT\textfile\shell\open\command
has a reference to SendToPS.exe

I have an old Windows 10 machine here and it had a remnant 2019 entry (this is an old development machine) which has no discernible effect.

Was there a PrimalScript 2019 or a prior version installed on this particular machine? It is possible that this was changed a few years ago and is just lingering.
I do not have your entries and the context menu still shows the desired command.

Statistics: Posted by Alexander Riedel — Wed Jan 17, 2024 7:37 pm

---