Application.ExecutablePath returns different casing

Asked Nov 09 '17 at 08:32

Active Nov 09 '17 at 08:32

Viewed 71 times

recently I stumbled upon this:

In my app I'm using Application.ExecutablePath. Interestingly its return value seems not to be consistent. If I start the app directly it returns D:/path/to/app.exe, but if I start it using the debugger it returns D:/path/to/app.EXE.

It is not an actual problem, because I can use ToLower() and do what I want.

But I was wondering if anyone knows a reasonable explanation for this behaviour, as stated here it seems not the only inconsistancy with Application.ExecutablePath.

Thanks

asked Nov 09 '17 at 08:32

casiosmu

Windows doesnt care for casing.. – BugFinder Nov 09 '17 at 08:33
I know, but the question remains, why the exact same function should return different values – casiosmu Nov 09 '17 at 08:35
It probably reflects what the path was when used to start the process, in other words, the debugger told Windows to start app.EXE. – Lasse V. Karlsen Nov 09 '17 at 08:39

Application.ExecutablePath returns different casing

0 Answers0