wrong modulePath when symLink

[Hurdet]

I have a file.exe in c:\test
compiled with:

Code: Select all

wchar_t modulePath[MAX_PATH];
GetModuleFileName(NULL, modulePath, MAX_PATH);
MessageBox(0, modulePath, 0, 0);

I create a symlink to c:\test\file.exe in d:\test2\file.exe
If I run d:\test2\file.exe from cmd I get same path d:\test2\file.exe
instead if I run same file from TotalCommander internal association I get c:\test\file.exe
Do it is a bug?

[Horst.Epp]

I don't understand.
For what reason do you need an TC internal association
to open a symlink ?

[ghisler(Author)]

The Windows function ShellExecuteEx seems to do this - I'm passing the link name to it, but it opens the link target. I have tried this with a target file test.docx and a link linkname.docx. It opens in LibreOffice here on Windows 11 and shows test.docx in the title. Even when I rename the link to linkname.txt, it opens in LibreOffice and shows test.docx in the title.

[Hurdet]

There is a lot of work to switch to CreateProcess?

[ghisler(Author)]

CreateProcess has its own shortcomings, like not working with elevation.