Visual Studio: differentiate app.config for debug and release mode

Question

Is there a way to automatically use a separate app.config when building in release mode?

In other words, I want to test with one app.config, and release with another.

Currently, I keep a separate copy called app.config.production, and manually overwrite bin\Release\Application.exe.config after building for release.

score 44 · Answer 1 · edited Dec 30 '19 at 22:46

44

Unload the project in Solution Explorer via the context menu.

Edit the .csproj file via the context menu and add this:

<PropertyGroup>
    <AppConfig>App.$(Configuration).config</AppConfig>
</PropertyGroup>

edited Dec 30 '19 at 22:46

plr108

1,151
10
16

answered May 16 '18 at 14:45

trueboroda

2,390
24
24

1

although intellisense does not show appconfig as a valid property. It's works. I think it is most useful in the final stage of development, when no more major changes are needed in the app.config file. thanks – antonio Feb 01 '19 at 03:02

score 19 · Answer 2 · edited May 23 '17 at 10:29

I have recently posted a supremely belated response to a similar SO topic: https://stackoverflow.com/a/27546685/2798367

I will repeat it here for clarity:

This is somewhat late to the party, but I stumbled upon a nice way of implementing the web.transform approach for app.config files. (i.e. it makes use of the namespace http://schemas.microsoft.com/XML-Document-Transform)

I think it is "nice" because it is a pure xml approach and doesn't require 3rd party software.

A parent / default App.config file is descended from, according to your various build configurations. These descendants then only override what they need to. In my opinion this is much more sophisticated and robust than having to maintain x number of config files which get copied in their entirety, such as in other answers.

A walkthrough has been posted here: http://mitasoft.wordpress.com/2011/09/28/multipleappconfig/

Look, Mom - No explicit post-build events in my IDE!

For VS 2017, `v10.0` has to be replaced with `v15.0` in `` in the walk-through above. — Jean-François Beauchamp, Aug 31 '18 at 15:25

score 9 · Answer 3 · answered Nov 26 '15 at 10:01

9

A simple and fast way is to create a second file "App.release.config" and insert this pre-build event:

IF $(ConfigurationName) == Release COPY /Y "$(ProjectDir)App.config" "$(ProjectDir)App.debug.config"
IF $(ConfigurationName) == Release COPY /Y "$(ProjectDir)App.release.config" "$(ProjectDir)App.config"

And this post build event:

IF $(ConfigurationName) == Release COPY /Y "$(ProjectDir)App.debug.config" "$(ProjectDir)App.config"

This might be a bit odd, but it will allow you to keep using the .Settings files as debug settings, that are still linked to the App.config. The App.release.config must be build by hand, but it's pretty easy to switch this functionality.

answered Nov 26 '15 at 10:01

Martin Braun

8,191
8
54
91

where do you add these build events? – Adrian Jun 29 '17 at 20:21
2

@Adrian Right click your project in your solution, click on "Properties" and open the tap "Build Events" – Martin Braun Jul 03 '17 at 12:47
1

I really like this, simple and effective and doesnt rely on msbuild magic which tends to change over time. – rollsch Apr 27 '20 at 06:23

score 8 · Answer 4 · answered Aug 18 '16 at 15:50

8

I highly recommend SlowCheetah for app.config transformations. Visit this nuget gem here Visual Studio Gallery

answered Aug 18 '16 at 15:50

Rudy Hinojosa

1,360
13
14

Side Note: SlowCheetah only works when you publish your works, not when debugging. – Rudy Hinojosa Mar 19 '18 at 15:18
1

that is no longer the case – MickyD Jul 31 '18 at 07:44
2

Nice! I was hoping that change would come down the pike soon. – Rudy Hinojosa Aug 08 '18 at 19:31
SlowCheetah is a much better solution than Pre build / Post build scripting. – Sunny Tambi Feb 04 '20 at 14:37

score 4 · Answer 5 · answered Apr 27 '20 at 05:57

Similar to top answer but with this approach you can see the actual file if preferred and intellisense doesn't complain in csproj file:

  <Target Name="SetAppConfig" BeforeTargets="Compile">
    <Copy SourceFiles="debug.config" DestinationFiles="app.config" OverwriteReadOnlyFiles="true" Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' " />
    <Copy SourceFiles="release.config" DestinationFiles="app.config" OverwriteReadOnlyFiles="true" Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' " />
  </Target>

Matthieu H · Answer 6 · 2021-07-09T08:57:22.963

A clean solution is to group 2 files App.Debug.config and App.Release.config into App.config and change the good file into App.config depending on the configuration at compile time:

<ItemGroup>
    <None Include="App.config" />
    <None Include="App.Debug.config">
        <DependentUpon>App.config</DependentUpon>
    </None>
    <None Include="App.Release.config">
        <DependentUpon>App.config</DependentUpon>
    </None>
</ItemGroup>
<Target Name="SetAppConfig" BeforeTargets="Compile">
    <Copy SourceFiles="App.Debug.config" DestinationFiles="App.config" OverwriteReadOnlyFiles="true" Condition=" '$(Configuration)' == 'Debug' " />
    <Copy SourceFiles="App.Release.config" DestinationFiles="App.config" OverwriteReadOnlyFiles="true" Condition=" '$(Configuration)' == 'Release' " />
</Target>

With this solution you will get something like this in Visual Studio:

score 1 · Answer 7 · answered Jan 15 '16 at 16:40

1

I don't know if this helps, but app.config will recognise the standard MSBUILD substitution strings such as $(Configuration).

answered Jan 15 '16 at 16:40

Dave

2,927
2
23
27

Visual Studio: differentiate app.config for debug and release mode

7 Answers7

Linked