And there the problem lies: If the config file is right next to the exe, I wish to know where the exe is determined. BUT, plainly when I have all of the app built into a single EXE like this, . NET actually extracts the embedded DLL to a couple temporary place in my filesystem, then runs it from there. Every method for discovering the startup meeting’s vicinity I have found, either by googling or exploring with mirrored image while it runs, only gives me the location in the temp listing, not the only where the app was in fact introduced from. The app then makes an attempt to load the config file from this temp listing, which obviously fails.