blocks|key|1669587|text|我最近对一个类似的SO话题发布了一个非常迟的回复：https://stackoverflow.com/a/27546685/2798367|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1669588|为了清楚起见，我在这里重复一遍：|1669589|这有点晚了，但我偶然发现了一种为app.config文件实现web.transform方法的好方法。(例如，它使用名称空间http://schemas.microsoft.com/XML-Document-Transform)|style|CODE|1669590|我认为它很“好”，因为它是一种纯方法，不需要第三方软件。|BOLD|1669591|根据您的各种构建配置，会派生出一个父/默认App.config文件。然后，这些后代只会覆盖它们需要的内容。在我看来，这比必须维护x数量的配置文件要复杂和健壮得多，这些配置文件被完整地复制，例如在其他答案中。|1669592|已在此处发布演练：http://mitasoft.wordpress.com/2011/09/28/multipleappconfig/|1669593|1669594|听着，妈妈-在我的IDE中没有显式的构建后事件！|1669595|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/27546685/2798367|1|http://mitasoft.wordpress.com/2011/09/28/multipleappconfig/^0|P|18|0|0|0|G|A|U|D|1P|1F|0|G|C|0|1S|1|0|9|1N|1|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|18|8|@$A|19|B|1A|H|I]|$A|1B|B|1C|H|I]|$A|1D|B|1E|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1F|8|@$A|1G|B|1H|H|L]]|9|@]|C|$]]|$1|M|3|N|5|6|7|1I|8|@$A|1J|B|1K|H|I]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@$A|1M|B|1N|1|1O]]|C|$]]|$1|Q|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1R|8|@]|9|@]|C|$]]]|U|$V|$5|W|X|Y|C|$Z|10]]|11|$5|W|X|Y|C|$Z|12]]]]

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

I will repeat it here for clarity:

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

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 <code>x</code> number of config files which get copied in their entirety, such as in other answers.

A walkthrough has been posted here: <a href="http://mitasoft.wordpress.com/2011/09/28/multipleappconfig/" rel="noreferrer">http://mitasoft.wordpress.com/2011/09/28/multipleappconfig/</a>

<hr>

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

blocks|key|2098214|text|一种简单而快速的方法是创建第二个文件"App.release.config“，并插入此预构建事件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2098215|IF+$(ConfigurationName)+==+Release+COPY+/Y+"$(ProjectDir)App.config"+"$(ProjectDir)App.debug.config"
IF+$(ConfigurationName)+==+Release+COPY+/Y+"$(ProjectDir)App.release.config"+"$(ProjectDir)App.config"|code-block|syntax|javascript|2098216|和这个构建后事件：|2098217|IF+$(ConfigurationName)+==+Release+COPY+/Y+"$(ProjectDir)App.debug.config"+"$(ProjectDir)App.config"|2098218|这可能有点奇怪，但它将允许您继续使用仍然链接到App.config的.Settings文件作为调试设置。App.release.config必须手动构建，但是切换此功能非常容易。|offset|length|style|CODE|2098219|entityMap^0|0|0|0|0|N|A|Y|9|1G|I|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]|$M|Z|N|10|O|P]|$M|11|N|12|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

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

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

And this post build event: 

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

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

blocks|key|2098227|text|我不知道这是否有帮助，但app.config将识别标准的MSBUILD替换字符串，如$(配置)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2098228|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|5626979|text|对于app.config转换，我强烈推荐使用SlowCheetah。请访问此处的nuget+gem+Visual+Studio+Gallery|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5626980|entityMap|0|LINK|mutability|MUTABLE|url|https://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5/^0|1E|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I highly recommend SlowCheetah for app.config transformations. Visit this nuget gem here <a href="https://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5/" rel="noreferrer">Visual Studio Gallery</a>

blocks|key|1669614|text|通过上下文菜单在解决方案资源管理器中卸载项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1669615|通过上下文菜单编辑.csproj文件，并添加以下内容：|offset|length|style|CODE|1669616|<PropertyGroup>
++++<AppConfig>App.$(Configuration).config</AppConfig>
</PropertyGroup>|code-block|syntax|javascript|1669617|entityMap^0|0|9|7|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Unload the project in Solution Explorer via the context menu. 

Edit the <code>.csproj</code> file via the context menu and add this:

<pre><code>&lt;PropertyGroup&gt;
 &lt;AppConfig&gt;App.$(Configuration).config&lt;/AppConfig&gt;
&lt;/PropertyGroup&gt;
</code></pre>

blocks|key|5627047|text|类似于top答案，但使用这种方法，如果您愿意，可以看到实际的文件，并且intellisense不会在csproj文件中出现问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5627048|++<Target+Name="SetAppConfig"+BeforeTargets="Compile">
++++<Copy+SourceFiles="debug.config"+DestinationFiles="app.config"+OverwriteReadOnlyFiles="true"+Condition="+'$(Configuration)%7C$(Platform)'+==+'Debug%7CAnyCPU'+"+/>
++++<Copy+SourceFiles="release.config"+DestinationFiles="app.config"+OverwriteReadOnlyFiles="true"+Condition="+'$(Configuration)%7C$(Platform)'+==+'Release%7CAnyCPU'+"+/>
++</Target>|code-block|syntax|javascript|5627049|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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

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

blocks|key|4209164|text|一个干净的解决方案是将2个文件App.Debug.config和App.Release.config分组到App.config中，并根据编译时的配置将好的文件更改为App.config：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4209165|<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>|code-block|syntax|javascript|4209166|使用此解决方案，您将在Visual+Studio中获得类似以下内容：|4209167|​|4209168|📷|atomic|4209169|4209170|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1749d0a9193109b2e6813d9254ee7f0e.png|imageAlt^0|F|G|W|I|1H|A|2A|A|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1C|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|R|3|N|5|6|7|1H|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z|10|-4]]]]

A clean solution is to group 2 files <code>App.Debug.config</code> and <code>App.Release.config</code> into <code>App.config</code> and change the good file into <code>App.config</code> depending on the configuration at compile time:
<pre class="lang-xml prettyprint-override"><code>&lt;ItemGroup&gt;
 &lt;None Include=&quot;App.config&quot; /&gt;
 &lt;None Include=&quot;App.Debug.config&quot;&gt;
 &lt;DependentUpon&gt;App.config&lt;/DependentUpon&gt;
 &lt;/None&gt;
 &lt;None Include=&quot;App.Release.config&quot;&gt;
 &lt;DependentUpon&gt;App.config&lt;/DependentUpon&gt;
 &lt;/None&gt;
&lt;/ItemGroup&gt;
&lt;Target Name=&quot;SetAppConfig&quot; BeforeTargets=&quot;Compile&quot;&gt;
 &lt;Copy SourceFiles=&quot;App.Debug.config&quot; DestinationFiles=&quot;App.config&quot; OverwriteReadOnlyFiles=&quot;true&quot; Condition=&quot; '$(Configuration)' == 'Debug' &quot; /&gt;
 &lt;Copy SourceFiles=&quot;App.Release.config&quot; DestinationFiles=&quot;App.config&quot; OverwriteReadOnlyFiles=&quot;true&quot; Condition=&quot; '$(Configuration)' == 'Release' &quot; /&gt;
&lt;/Target&gt;
</code></pre>
With this solution you will get something like this in Visual Studio:
<a href="https://i.stack.imgur.com/Mp7ro.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Mp7ro.png" alt="screenshot" /></a>

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.

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在发布模式下构建时，有没有办法自动使用单独的app.config？换句话说，我想用一个app.config测试，然后用另一个发布。目前，我保留了一个单独的副本，名为app.config.production，并在构建发布后手动覆盖bin\Release\Application.exe.config。

问Visual Studio:区分调试模式和发布模式的app.config
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio:区分调试模式和发布模式的app.configEN