ExtractFilePath v TDirectory.GetCurrentDirectory

[Ian Branch 128]

Hi Team,

In a simple Win32 App, when might ExtractFilePath(Application.ExeName) not be the same as TDirectory.GetCurrentDirectory if called in the Main Form??

 

Regards & TIA,

Ian

[Lajos Juhász 295]

The program was started with a different current folder option, or the WIN API SetCurrentDirectory was called somewhere from the application.

[Ian Branch 128]

Tks Lajos,

Neither apply in my situation.

 

Ian

[haentschman 92]

Hi...

https://docwiki.embarcadero.com/Libraries/Seattle/en/System.IOUtils.TDirectory.GetCurrentDirectory

Quote

Returns the current working directory.

Use GetCurrentDirectory to get the current directory

Current working directory:  99% <> ExtractFilePath(Application.ExeName) 

Quote

or the WIN API SetCurrentDirectory was called somewhere

Example: Current working directory can be "C:\Windows\System32" or else a special folder...

 

[Fr0sT.Brutal 900]

1 hour ago, Ian Branch said:

Neither apply in my situation.

Start it via shortcut and prepare for surprise

[David Heffernan 2354]

2 hours ago, Ian Branch said:

Tks Lajos,

Neither apply in my situation.

 

Ian

This can only be true if you are the only person ever to run your program.

 

These two things, the directory containing the executable and the working directory are completely different and unrelated things. Generally you don't want to use the working directory in a GUI program. It's really only useful in a console app where you can think of the working directory as one of the inputs to the process.

 

What problem are you actually trying to solve?

[SwiftExpat 65]

My experience it is one of these:

command line is different dir than exe

 

Short cut start in:

[Ian Branch 128]

Hi Guys,

Thank you for your inputs.

I wasn't trying to solve any particular problem, just curious.

 

Ian