tag:support.appharbor.com,2010-11-23:/discussions/problems/56273-application-environmentAppHarbor: Discussion 2018-10-19T03:07:09Ztag:support.appharbor.com,2010-11-23:Comment/328205362014-05-04T00:51:54Z2014-05-04T00:51:54ZApplication Environment<div><p>Hi,</p>
<p>The <code>Environment</code> appSetting isn't related to whether
your application has debugging enabled or not - it's just a regular
app setting that is applied and does nothing further.</p>
<p>However, it's likely that the <code>debug</code> attribute of
the <code>compilation</code> element is set to <code>true</code> in
your <code>Web.config</code>. That's the default configuration, but
usually a <code>Web.Release.config</code> removes this attribute.
Since we apply the transformation that matches the environment name
(by default "Release") this causes the application to be de
deployed without debugging enabled. I wonder if this configuration
is somehow missing from your application?</p>
<p>You could also just try and set the <code>debug</code> attribute
to <code>false</code> and see if that resolves the issue you're
seeing.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/328205362014-08-29T10:30:39Z2014-08-29T10:30:39ZApplication Environment<div><p>I've created a new empty asp.net application and deployed it to
appharbor to see if the transformation occurs, but no success. I've
downloaded the build from appharbor in order to inspect the
resulting web.config compilation debug=true. What's wrong?</p>
<p>In the git source code repository I have the 3 files:
web.config, web.config.debug and web.config.release. What am I
missing?</p></div>jpolvoratag:support.appharbor.com,2010-11-23:Comment/328205362014-08-29T17:18:12Z2014-08-29T17:18:12ZApplication Environment<div><p>Hi,</p>
<p>The release transformations, configuration variables are not
applied to your build artifact until it's deployed, so you
shouldn't see any transformations there. I took a look at the build
and the <code>Web.Release.config</code> is missing from the output
directory. That's also why it's not applied when the build is
deployed, and you can resolve it by setting the <code>Build
Action</code> attribute on the <code>Web.Release.config</code> file
reference to <code>Content</code>.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/328205362014-08-29T23:36:10Z2014-08-29T23:36:10ZApplication Environment<div><p>Thanks, I didn't know this. Now I will update all my projects to
include Web.*.config files as "Content".</p>
<p>This information is very important, I believe, for all appharbor
users and I suggest that should be clarified in some doc/tutorial
for starters.</p></div>jpolvora