blocks|key|583061|text|排除web.config文件不是推荐的解决方案。您应该使用web.config转换文件，这是web.xxx.config文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583062|​|583063|📷|atomic|offset|length|583064|583065|发布网站时，Visual将将本地web.config与相应的web.xxx.config文件合并|583066|配置转换文件使用XDT+(XML文档转换)语法。例如，如果要更改连接字符串，可以在转换文件中使用以下代码：|583067|<?xml+version="1.0"?>
<configuration+xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
++<connectionStrings>
++++<add+name="MyDB"+
+++++++++connectionString="value+for+the+deployed+Web.config+file"+
+++++++++xdt:Transform="SetAttributes"+xdt:Locator="Match(name)"/>
++</connectionStrings>|code-block|syntax|javascript|583068|有关更多示例和信息，请参见使用Visual实现网络项目部署的Web.config转换语法。|583069|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/7878b0498d6ce51216bdb2b15a29538e.png|imageAlt|1|LINK|MUTABLE|url|https://msdn.microsoft.com/en-us/library/dd465326(v=vs.110).aspx^0|0|0|0|1|0|0|0|0|0|0|D|V|1|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@$G|1B|H|1C|1|1D]]|A|$]]|$1|I|3|C|5|6|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1H|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1I|8|@]|9|@$G|1J|H|1K|1|1L]]|A|$]]|$1|U|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]|13|$5|14|Y|15|A|$16|17]]]]

Excluding the web.config file is not the recommended solution. You should use web.config transformation file instead, this is the web.xxx.config file. 

<img src="https://i.stack.imgur.com/X9bCn.png" alt="Example of transformation configuration file">

When you publish your website, Visual Studio will merge your local web.config with the corresponding web.xxx.config file

The config transform file use XDT (XML Document Transform) syntax. For example, if you want to change your connectionstring, you can use this piece of code in you transformation file : 

<pre class="lang-xml prettyprint-override"><code>&lt;?xml version="1.0"?&gt;
&lt;configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"&gt;
 &lt;connectionStrings&gt;
 &lt;add name="MyDB" 
 connectionString="value for the deployed Web.config file" 
 xdt:Transform="SetAttributes" xdt:Locator="Match(name)"/&gt;
 &lt;/connectionStrings&gt;
</code></pre>

See <a href="https://msdn.microsoft.com/en-us/library/dd465326(v=vs.110).aspx" rel="nofollow noreferrer">Web.config Transformation Syntax for Web Project Deployment Using Visual Studio</a> for more examples and information.

blocks|key|2924985|text|只需选择web.config属性，将“构建操作”更改为“无”，将“复制到输出目录”更改为“不复制”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2924986|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|$]]

Simply select the web.config properties and change 'Build Action' to 'None' and 'Copy To Output Directory' to 'Do Not copy'

blocks|key|2925038|text|我知道这是一个旧的帖子，有旧的答案，但对我来说，两种描述的解决方案都是错误的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2925039|当操作环境凭据时，Web.config版本会带来安全风险，而"Build“=”None“解决方案会破坏在本地调试项目的可能性，因为Web.Config文件永远不会出现在"bin”目录中。|offset|length|style|BOLD|2925040|这里描述的是一个更干净的解决方案：|2925041|https://learn.microsoft.com/fr-fr/aspnet/web-forms/overview/deployment/advanced-enterprise-web-deployment/excluding-files-and-folders-from-deployment|2925042|它基本上是创建一个ProjectName.wpp.targets文件，其中包含要在发布项目时排除的文件/文件夹列表。|2925043|要从名为Blog.wpp.targets的项目中删除Web.config，您需要创建一个名为的文件，如下所示：|2925044|文件：Blog.wpp.targets|CODE|2925045|<?xml+version="1.0"+encoding="utf-8"+?>
<Project+ToolsVersion="4.0"
+++++++++xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
++<ItemGroup>
++++<ExcludeFromPackageFiles+Include=".\Web.config">
++++++<FromTarget>Blog.wpp.targets</FromTarget>
++++</ExcludeFromPackageFiles>
++</ItemGroup>
</Project>|code-block|syntax|javascript|2925046|无需更改项目或.csproj文件中的任何内容。|2925047|entityMap|0|LINK|mutability|MUTABLE|url^0|0|25|G|0|0|H|0|0|45|0|45|0|0|0|1M|0|0|1J|0|0|J|3|G|0|0|0|N|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|L|3|M|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1P|8|@$D|1Q|E|1R|F|G]|$D|1S|E|1T|F|R]]|9|@]|A|$]]|$1|S|3|T|5|U|7|1U|8|@]|9|@]|A|$V|W]]|$1|X|3|Y|5|6|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|K]]]]

I know this is an old post, with old answers but to me, both described solutions are wrong.

Web.config flavors induces a security risk when manipulating environments credentials, and the "Build Action"="None" solution, breaks the possibility to debug the project locally,as the Web.Config file will never be present in the "bin" directory.

A cleaner solution is what is described here :

<a href="https://learn.microsoft.com/fr-fr/aspnet/web-forms/overview/deployment/advanced-enterprise-web-deployment/excluding-files-and-folders-from-deployment" rel="noreferrer">https://learn.microsoft.com/fr-fr/aspnet/web-forms/overview/deployment/advanced-enterprise-web-deployment/excluding-files-and-folders-from-deployment</a>

which is basically to create a ProjectName.wpp.targets file, containing a list of files / folders to exclude when publishing your project.

To remove the Web.config from a project named Blog you would need to create a file named Blog.wpp.targets with something like this:

File: <code>Blog.wpp.targets</code>

<pre><code>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;Project ToolsVersion="4.0"
 xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt;
 &lt;ItemGroup&gt;
 &lt;ExcludeFromPackageFiles Include=".\Web.config"&gt;
 &lt;FromTarget&gt;Blog.wpp.targets&lt;/FromTarget&gt;
 &lt;/ExcludeFromPackageFiles&gt;
 &lt;/ItemGroup&gt;
&lt;/Project&gt;
</code></pre>

No need to change anything in your project or .csproj file.

blocks|key|1626252|text|使用AspCore项目，然后尝试在.csproj中添加以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1626253|<PropertyGroup>
++<TargetFramework>netcoreapp2.2</TargetFramework>
++<IsTransformWebConfigDisabled>true</IsTransformWebConfigDisabled>
</PropertyGroup>|code-block|syntax|javascript|1626254|请参阅https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#webconfig-file|offset|length|1626255|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#webconfig-file^0|0|0|3|2T|0|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|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

2020 and using AspCore project, then try to add below code in your .csproj:
<pre><code>&lt;PropertyGroup&gt;
 &lt;TargetFramework&gt;netcoreapp2.2&lt;/TargetFramework&gt;
 &lt;IsTransformWebConfigDisabled&gt;true&lt;/IsTransformWebConfigDisabled&gt;
&lt;/PropertyGroup&gt;
 
</code></pre>
Refer to <a href="https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#webconfig-file" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#webconfig-file</a>

blocks|key|2925137|text|如果您要从Visual发布到Azure+App+Services+(我使用的是2019年)，并且没有将web.config的Build设置为“none”，那么每次都可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2925138|右键单击项目，选择“发布”。然后点击“预览更改”。|ordered-list-item|2925139|📷|atomic|offset|length|2925140|然后取消检查web.config文件，这样它就不会被发布。你也将有机会回顾即将出版的内容。|2925141|​|2925142|2925143|2925144|我这样做是因为我发布到多个实例，并且每个实例都有不同的版本。通过这种方式，我每次都可以查看web.config，以确保是否添加了任何附加的AppSettings配置，我将注意到这一点。|2925145|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/ccf83b94dfdf05546f6d0a6a25089944.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/79a4073304d5b2144092dcb5da57fdff.png^0|0|0|0|1|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|14|8|@]|9|@$H|15|I|16|1|17]]|A|$]]|$1|J|3|K|5|D|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|F|5|G|7|1A|8|@]|9|@$H|1B|I|1C|1|1D]]|A|$]]|$1|O|3|M|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]|10|$5|U|V|W|A|$X|11|Z|-4]]]]

If you're publishing to Azure App Services from Visual Studio (I'm using 2019), and didn't set the web.config's Build Action to 'none', you can do this every time:
<ol>
<li>Right click on your project, select publish. Then click on &quot;Preview Changes&quot;.
<a href="https://i.stack.imgur.com/89oqO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/89oqO.png" alt="enter image description here" /></a>
</li>
<li>Then un-check the web.config file so it does not get published. You'll get a chance to review what will be publish too.
</li>
</ol>
<a href="https://i.stack.imgur.com/Zfmgg.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Zfmgg.png" alt="enter image description here" /></a>
I am doing this because I publish to multiple instances and each instances are of different version. This way I get to review the web.config everytime to make sure if there's any additional AppSettings configuration added, I will be aware of it.

blocks|key|1626328|text|对于遗留的ASP.NET+Web应用程序，请将<ExcludeFilesFromDeployment>Web.config</ExcludeFilesFromDeployment>添加到在Properties\PublishProfiles文件夹中找到的适当的.xmlpub配置文件中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1626329|<Project>
++++<PropertyGroup>++++++++++++++++++++++++++
++++++++<ExcludeFilesFromDeployment>Web.config</ExcludeFilesFromDeployment>+++++++++++++
++++</PropertyGroup>
</Project>++|code-block|syntax|javascript|1626330|entityMap^0|N|1V|2M|Q|3M|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

For an legacy ASP.NET Web Application, add <code>&lt;ExcludeFilesFromDeployment&gt;Web.config&lt;/ExcludeFilesFromDeployment&gt;</code> to the appropriate <code>.xmlpub</code> profile file found in the <code>Properties\PublishProfiles</code> folder.
<pre><code>&lt;Project&gt;
 &lt;PropertyGroup&gt; 
 &lt;ExcludeFilesFromDeployment&gt;Web.config&lt;/ExcludeFilesFromDeployment&gt; 
 &lt;/PropertyGroup&gt;
&lt;/Project&gt; 


 
</code></pre>

When using the "Publish Web Site" feature in Visual Studio 2013. How can you exclude publishing the web.config so that it doesn't overwrite the server web.config?

The question is identical to the following except the VS version.

<a href="https://stackoverflow.com/questions/1288858/how-to-exclude-web-config-when-publishing-with-visual-web-developer-express">How to exclude web.config when publishing with Visual Web Developer Express?</a>

However, its solution does not apply to VS2013. "Build Action" option cannot be found in VS2013. And setting "ExcludeFilesFromDeployment" causes compile problems.

How to exclude web.config when publishing with Visual Studio 2013?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在Visual 2013中使用“发布网站”功能时。如何排除发布web.config，使其不覆盖服务器web.config？除VS版本外，该问题与下面的问题相同。然而，它的解决方案不适用于VS2013。在VS2013中找不到“生成操作”选项。设置"ExcludeFilesFromDeployment“会导致编译问题。

问使用Visual 2013发布时如何排除web.config？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Visual 2013发布时如何排除web.config？EN