Hi,
The issue of App.Config probing is explained in developer guide, but still I am not sure if this has been asked before.
Instead of probing *.exe.config, is there a reason why the executing assembly's .exe.config is not taken as the highest priority?
For example, I have a.exe and b.exe, and a.exe.config and b.exe.config, all in one deployment folder. There is often a confusion which exe.config the exe will load.
Thanks.
Sebastian