tag:support.appharbor.com,2010-11-23:/discussions/problems/1706-using-configsource-for-appsettings-and-connectionstrings-in-webconfig-not-workingAppHarbor: Discussion 2011-12-20T13:41:11Ztag:support.appharbor.com,2010-11-23:Comment/119896342011-12-08T22:44:45Z2011-12-08T22:44:45ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>Hi Mark</p>
<p>We haven't encountered this problem before. We'll investigate
and try to come up with a scheme that works for scenarios like
yours.</p>
<p>Thanks for reporting this.<br>
Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/119896342011-12-09T15:43:31Z2011-12-09T15:43:31ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>I have a work-around for now, but I would like to go back to the
other way. Please let me know when you have this figured out.</p>
<p>Thanks,<br>
Mark</p></div>articulatetag:support.appharbor.com,2010-11-23:Comment/119896342011-12-09T15:49:13Z2011-12-09T15:49:13ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>Are you using the .NET library to read the configuration values
or do you also parse the files manually?</p>
<p>I'm thinking that since we can't apply partial transformations,
we could combine the configuration file into a single document
before executing the transformations, but this will break anything
that relies on the individual files.</p></div>tttag:support.appharbor.com,2010-11-23:Comment/119896342011-12-09T18:03:53Z2011-12-09T18:03:53ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>This is using the standard web.config processes. I have no code
to read the secondary files. See this post: <a href=
"http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx">
http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configso...</a>
and this one <a href=
"http://www.nikhilk.net/Entry.aspx?id=158">http://www.nikhilk.net/Entry.aspx?id=158</a></p>
<p>The only transformation that I am doing is to change the name of
the entry in the configSource attribute to use the appropriate
file. Here is what the transformations look like:</p>
<pre>
<code><appSettings xdt:Transform="SetAttributes" configSource="AppSettings.production.config" />
<connectionStrings xdt:Transform="SetAttributes" configSource="ConnectionStrings.production.config" /></code>
</pre></div>articulatetag:support.appharbor.com,2010-11-23:Comment/119896342011-12-16T16:29:35Z2011-12-16T16:29:35ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>Hi Mark</p>
<p>If you add this is a suggestion on the <a href=
"https://appharbor.com/feedback">feedback forum</a> we'll extend
the configuration file handling as soon as we find time.</p>
<p>Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/119896342011-12-20T13:26:27Z2011-12-20T13:26:27ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>Here it is: <a href=
"http://feedback.appharbor.com/forums/95687-general/suggestions/2464415-support-configsource-in-web-config-specifically-i">
http://feedback.appharbor.com/forums/95687-general/suggestions/2464...</a></p></div>articulatetag:support.appharbor.com,2010-11-23:Comment/119896342011-12-20T13:41:09Z2011-12-20T13:41:09ZUsing configSource for appSettings and connectionStrings in web.config not working<div><p>Great, we'll keep you posted.</p>
<p>Michael</p></div>friism