Does the order of elements in app.config matter?

Here you have the entire explanation of the web config. The order and the requiered tag.

Up vote 2 down vote favorite share g+ share fb share tw.

I have seen and experienced problems with app. Config/web. Config where I had changed the order of elements and the app stopped working.

I believe I fixed the problem by looking at machine. Config and following the order in there. One example is the following question: Common.

Logging config exception The issue was resolved by changing the order the elements appear in the file. So, the question is, does the order of elements matter? It appears to me it does.

If it does, is it documented anywhere, an xsd schema maybe? .net web-config app-config configuration-files link|improve this question edited Jul 21 '11 at 18:07 asked Jul 21 '11 at 17:55Klinger2,265715 100% accept rate.

Here you have the entire explanation of the web config. The order and the requiered tag. msdn.microsoft.com/en-us/library/ackhksh....

It appears that at least for the configSections element order does matter. Document msdn.microsoft.com/en-us/library/ms22825... states the following: "If the configSections element is in a configuration file, the configSections element must be the first child element of the configuration element. " I got this from here: social.msdn.microsoft.com/Forums/en-US/c....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.