PS5.1 and in a parallel PS7x items are needed

[gh-Destiny]

HI!

Your tool is perfectly useful and precisely working.
BUT! very often for PS1 scripts we need to run them OR inside the PowerShell classical app v.5.1
OR inside the modern one - PowerShell 7x! And right now with help of your tool this is impossible to do.
Because it supports only ONE variable - PowerShellHere with only ONE exe path. Only one console....

So if I may - I would like to ask you to create a new support for TWO variants of this console
in the independent variant - i.e. in the drop-down context menu there should be another nested block
with the PowerShell call menu - and inside this submenu the user could finally choose as it is now:
one of three options: just open, open as Administrator, or open on behalf of TrustedInstaller.

I.e. once again, all we see in the main menu is "Open in PowerShell ...", then it has two submenus:
"Classical 5.1 ..." and "Modern Core 7.x ...".
And within each of these submenus are the standard three opening options of these consoles.

[LesFerch]

Yes, I need the same feature myself. It's already planned for the next release.

[gh-Destiny]

I also hope not to be too impudent - but if you consider improvements for the next release
then what about this: we know that in the usual context menu for PS1 files there is immediately a ready-made item
"Run with PowerShell" - and it works ONLY with the classic PS5.1 console/env.
And for 7.x, there is simply NO such menu item.
On the Internet someone writes that this is was done so because it was decided not to high load too much
this menu.... Very funny)))
So maybe you can do - well, I don't even know how to describe it exactly - a mini editor of this special single item
in the context menu? So that, firstly, it is possible to rename it under itself. For example like "Run with Classic PowerShell".
And secondly, so that we can add OUR own by analogy item "Run with PowerShell Core 7.x"? Of course, renaming and naming should work with that these lines are written in the registry somewhere to support the multilingualism of Windows itself.

I understand that this sounds strange compared to what I just wrote above. It seems that in doing so we are simply devaluing the first suggestion above. BUT it deeply seems to me that these are different levels of convenience for work. That is, you need to have the option to just launch the appropriate console for folder X. And separately - you need to be able to run the script IMMEDIATELY – without an intermediate console call. BUT taking into account the correct PowerShell option.
something like that:
https://www.tenforums.com/tutorials/181110-add-edit-run-ps1-file-context-menu-windows-10-a.html