title: ssis xml configurations - configs overwrite packages - does ssis change config without you telling it to?
body: <p>i worked all day yesterday trying to back out the impacts of an incorrect connection string in my XML config file. i went through each package, deleting the faulty connection manager and re-adding it with the correct server name. each time i did this i explicitly updated the configuration by removing it, then re-adding it with the overwrite option.  but then i made the horrible mistake of pulling up the parent package, which used a different xml config, which updated the connection manager  again to the wrong server name . </p>
  
  <p>i pulled the configurations out the parent package and started fixing the child packages again. having fixed the child packages, i called one of them from its now xml config free parent. i was really shocked and disappointed to see that it again had the wrong server in the connection. </p>
  
  <p>How could this happen? </p>
  
  <p>i also noticed through wordpad++ that the config file was  updated. my hypothesis is that when the parent's configuration updated the connection manager, SSIS <strong>automatically updated the now corrected config file</strong> and broke it again.</p>
  
  <p>does SSIS really update config files automatically when components of it change? is it really bidirectional like this? if so its totally confusing behavior - like a ping pong ball, or putting fingers in dykes. i am getting ready to recommend that we never use XML configurations!!.   </p>