blocks|key|2937564|text|您可以做的一件事是向.csproj或.vbproj文件添加一个条件，以便MSBuild在进行构建时进行检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2937565|该条件将检查是否正在进行发布，并检查构建是否为调试构建，然后执行诸如运行外部工具之类的操作，或者以其他方式中断构建过程或导致构建失败。|2937566|示例可能如下所示：|2937567|<Choose>
++++<When+Condition="+'$(Configuration)'=='Debug'+">
++++++++<Exec+Command="C:\foo.bat"+ContinueOnError="false"+/>
++++</When>
+</Choose>|code-block|syntax|javascript|2937568|其中foo.bat是返回非零的批处理文件，因此停止发布。|2937569|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

One thing you can do is add a condition to the .csproj or .vbproj file that MSBuild will check when doing a build. 

The condition would check if a publish is occurring and check if the build is a debug build, then do something like run an external tool or otherwise interrupt the build process or cause it to fail.

An example might be something like this:

<pre><code>&lt;Choose&gt;
 &lt;When Condition=" '$(Configuration)'=='Debug' "&gt;
 &lt;Exec Command="C:\foo.bat" ContinueOnError="false" /&gt;
 &lt;/When&gt;
 &lt;/Choose&gt;
</code></pre>

Where foo.bat is a batch file that return non-zero, thus stopping the publish from occurring.

blocks|key|721483|text|我选择了另一个对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|721484|我不能改变我的构建过程。所以我做了Tools→Customize...并更改操作的文本，添加类似"Publish+CONFIGURE+TO+RELEASE!“的警告，并在Debug/Release配置选项旁边放置Publish按钮。很简单!|721485|通过这样做，我大大降低了人为错误的风险。这些按钮应该始终放在一起。|721486|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have chosen another solution that worked for me:

I couldn't change my build process. So I did Tools → Customize... and change the text of the action, adding an alert like "Publish [CONFIGURE TO RELEASE!]", and placing the Publish button next to the Debug/Release configuration option. It's easy!

With this I considerably reduced the risk of human error. Those buttons should always be together.

blocks|key|3782909|text|我已经开始修改.csproj文件以包含以下代码，以便为调试部署抛出错误，从而有效地阻止部署的发生：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3782910|
<Target+Name="BeforePublish">
++++<Error+Condition="'$(DebugSymbols)'+==+'true'"+Text="You+attempted+to+publish+a+configuration+that+defines+the+DEBUG+constant!"+/>
</Target>|code-block|syntax|javascript|3782911|只需将它放在文件的末尾，就在</Project>标记之前。|offset|length|style|CODE|3782912|(原文来源：http://www.nathanpjones.com/wp/2010/05/preventing-clickonce-publishing-a-debug-configuration/comment-page-1/#comment-625)|3782913|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nathanpjones.com/wp/2010/05/preventing-clickonce-publishing-a-debug-configuration/comment-page-1/#comment-625^0|0|0|E|A|0|6|3C|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@$I|12|J|13|1|14]]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

I have started to modify the .csproj files to include the following code to throw an error for debug deploys, effectively preventing the deploy from happening:

<pre><code>&lt;!-- The following makes sure we don’t try to publish a configuration that defines the DEBUG constant --&gt;
&lt;Target Name="BeforePublish"&gt;
 &lt;Error Condition="'$(DebugSymbols)' == 'true'" Text="You attempted to publish a configuration that defines the DEBUG constant!" /&gt;
&lt;/Target&gt;
</code></pre>

Just place it at the end of the file, right before the <code>&lt;/Project&gt;</code> tag.

(original source: <a href="http://www.nathanpjones.com/wp/2010/05/preventing-clickonce-publishing-a-debug-configuration/comment-page-1/#comment-625">http://www.nathanpjones.com/wp/2010/05/preventing-clickonce-publishing-a-debug-configuration/comment-page-1/#comment-625</a>)

Is there a way to disallow publishing of debug builds with ClickOnce?

I only want to allow release builds through, but right now human error causes a debug build to slip through once in a while. 

We're publishing the build from within Visual Studio.

Disallow publishing of debug builds for ClickOnce deployment

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

有没有办法禁止使用ClickOnce发布调试版本？我只想允许发布构建通过，但现在人为错误导致调试构建偶尔滑过一次。我们将从Visual Studio中发布构建。

问不允许为ClickOnce部署发布调试版本
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不允许为ClickOnce部署发布调试版本EN