[ACCEPTED]-Configuration Manager only shows Debug-build-environment

ASP.NET web sites do not use the configuration 17 manager to determine if debug information 16 is included in the compile. You must set 15 it in the web.config file. Visual Studio will never 14 change debug to "false" for you automactially, as 13 far as I know.

Find this section in your 12 web.config file and change it to "false":

<!--
    Set compilation debug="true" to insert debugging
    symbols into the compiled page. Because this
    affects performance, set this value to true only
    during development.
-->

<compilation debug="true">

Visual Studio 11 will ask you if you want it changed from 10 false to true if you are running your web 9 site in the IDE, but unfortunately it does 8 not do the reverse for publishing (which 7 seems more important to me).

If you have 6 multiple projects in your solution, and 5 at least one of them supports a release 4 configuration (such as a DLL) - it will 3 appear in the configuration drop-down list. Building 2 with Release selected still does not affect 1 the website, however.

After reviewing the best answer and wrestling 12 with this problem for a couple of hours, I 11 ran across this answer. My solution was 10 to add a full application: usually use an 9 empty web site, but had the same problem 8 of the release not displaying. I added 7 a full application to the solution and it 6 then allowed me to deploy my project within 5 the solution, since adding the complete 4 application also added the option of 'release' in 3 the dropdown. I very much appreciate the 2 advice, but not sure why this tool is so 1 quirky. Thanks again for your suggestion.

The Configuration Manager for the Solution 10 allows you to delete either (or both) of 9 these default build configurations (through 8 the Edit... option you mention above). I 7 would bet that someone deleted the Release 6 configuration.

You can get it back by recreating 5 it, or copy the appropriate lines from a 4 solution you make from scratch real quick. A 3 file diff shows the following:

Default solution 2 file:

GlobalSection(SolutionConfigurationPlatforms) = preSolution
    Debug|Any CPU = Debug|Any CPU
    Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Debug|Any CPU.Build.0 = Debug|Any CPU
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Release|Any CPU.ActiveCfg = Release|Any CPU
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Release|Any CPU.Build.0 = Release|Any CPU
EndGlobalSection

Solution after I manually deleted the 1 Release configuration:

GlobalSection(SolutionConfigurationPlatforms) = preSolution
    Debug|Any CPU = Debug|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
    {EDD50911-B94E-49A4-A08B-A2E91228A04B}.Debug|Any CPU.Build.0 = Debug|Any CPU
EndGlobalSection

the process was changed, you just need to 4 check the 2 bottom check boxes during the 3 settings part of the publish process, as 2 shown in the image. in the bin folder you'll 1 find the dlls.

hope that helps

eiran