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

 

Right now we will look at all *.exe.config files in the executable folder, and I'm not sure if the order of the file list is determinate.  Once a "valid" (i.e., without errors) ideablade.configuration section is found and loaded, all further probing stops.