blocks|key|3255390|text|是的，它在项目的属性页的调试部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3255391|自2008年以来，在Visual+Visual+Studio中:右键单击项目，选择属性，转到调试部分--有一个用于“命令参数”的框。(提示:不是解决方案，而是项目)。|3255392|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Yes, it's in the Debugging section of the properties page of the project.

In Visual&nbsp;Studio since 2008: right-click the project, choose Properties, go to the Debugging section -- there is a box for "Command Arguments". (Tip: not solution, but project).

blocks|key|3255410|text|即使您确实在Visual+Studio外部启动了可执行文件，您仍然可以使用"Attach“命令将Visual+Studio连接到已经运行的可执行文件。这可能很有用，例如，当您的应用程序作为插件在另一个应用程序中运行时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3255411|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|$]]

Even if you do start the executable outside Visual Studio, you can still use the "Attach" command to connect Visual Studio to your already-running executable. This can be useful e.g. when your application is run as a plug-in within another application.

blocks|key|4100797|text|在Visual+Studio+2010中，右键单击项目，选择属性，单击左侧窗格中的配置属性部分，然后单击调试，然后在右侧窗格中有一个用于命令参数的框。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4100798|在其中输入命令行参数。你可以走了。现在进行调试并查看结果。如果您厌倦了在属性中进行更改，那么暂时直接在程序中提供输入。|4100799|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In Visual&nbsp;Studio&nbsp;2010, right click the project, choose Properties, click the configuring properties section on the left pane, then click Debugging, then on the right pane there is a box for command arguments.

In that enter the command line arguments. You are good to go. Now debug and see the result. If you are tired of changing in the properties then temporarily give the input directly in the program.

blocks|key|4100841|text|Microsoft+Visual+Studio+Ultima+2013。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4100842|您可以只转到DEBUG菜单→主属性→配置属性→调试，然后您将看到用于命令行参数的框。|4100843|实际上，您可以为所有不同的配置设置相同的输入参数，而不仅仅是为了调试。|4100844|从configuration的下拉菜单中选择:+All+Configurations并插入输入参数(每个参数用空格分隔)。|4100845|现在，您可以在不同的模式下执行您的程序，而不必每次都更改输入参数。|4100846|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Microsoft Visual Studio Ultima 2013.

You can just go to the DEBUG menu → Main Properties → Configuration properties → Debugging and then you will see the box for the command line arguments.

Actually, you can set the same input arguments for all the different configurations and not only for debugging.

From the pull down menu of configuration select: All Configurations and insert the input arguments (each argument separated by space).

Now, you can execute your program in different modes without having to change the input arguments every time.

blocks|key|3255565|text|在Visual+Visual+Studio的解决方案窗口中右键单击项目，选择“调试”(左侧)，并在“命令参数”字段中输入参数。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3255566|​|3255567|📷|atomic|offset|length|3255568|3255569|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/716272e390aa92d3bcd028ef25d9e59f.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Right click on the project in the Solution window of Visual&nbsp;Studio, select "Debugging" (on the left side), and enter the arguments into the field "Command Arguments":

<a href="https://i.stack.imgur.com/eMjKA.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/eMjKA.jpg" alt="Enter image description here"></a>

blocks|key|33840|text|在Visual+Studio2017中，使用.NET+Core控制台应用程序执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|33841|右键单击解决方案窗口中的项目，选择"Properties"，Debug+(左侧)，并在"Application+Arguments“字段中输入参数。|33842|请注意，它们应该用空格分隔。|33843|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/.NET_Core^0|M|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

In Visual Studio 2017 with a <a href="https://en.wikipedia.org/wiki/.NET_Core" rel="nofollow noreferrer">.NET Core</a> console application do the following:

Right click on the Project in the Solution window, select "Properties", Debug (on the left side), and enter the arguments into the field "Application Arguments".

Note that they should be space-separated.

blocks|key|3255642|text|这可能会帮助一些仍然有问题的人。我使用Visual+Studio2015，当我更改argv的定义时，我只能传递参数。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3255643|而不是|3255644|int+main(int+argc,+char+**argv){
}|code-block|syntax|javascript|3255645|我不得不用|3255646|int+main(int+argc,+char+*argv[]){
}|3255647|我不知道为什么它是必要的，但它是有效的。|3255648|entityMap^0|15|4|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

This may help some people who still have problems.
I use Visual Studio 2015 and I could only pass the arguments when I changed the definition of <code>argv</code>.

Instead of

<pre><code>int main(int argc, char **argv){
}
</code></pre>

I had to use

<pre><code>int main(int argc, char *argv[]){
}
</code></pre>

I do not know why it was necessary, but it works.

blocks|key|3255696|text|对于VS+2015和更高版本，请使用Smart+Command+Line+Arguments扩展。此插件添加了一个窗口，允许您打开和关闭参数：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3255697|​|3255698|📷|atomic|3255699|3255700|该扩展还将参数存储在JSON文件中，允许您将它们提交给源代码控制。除了确保您不必每次都键入所有参数之外，这还可以作为文档的有用补充，以供其他开发人员发现可用的选项。|3255701|entityMap|0|LINK|mutability|MUTABLE|url|https://marketplace.visualstudio.com/items?itemName=MBulli.SmartCommandlineArguments|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1f0116597326eccce239c344bc4846c3.png|imageAlt^0|I|S|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|I|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|U|P|V|C|$W|X|Y|-4]]]]

With VS 2015 and up, Use the <a href="https://marketplace.visualstudio.com/items?itemName=MBulli.SmartCommandlineArguments" rel="nofollow noreferrer">Smart Command Line Arguments</a> extension. This plug-in adds a window that allows you to turn arguments on and off:

<img src="https://mbulli.gallerycdn.vsassets.io/extensions/mbulli/smartcommandlinearguments/2.1.2/1554395906327/vsix_preview_image.png" alt="Smart Command Line Arguments interface">

The extension additionally stores the arguments in a JSON file, allowing you to commit them to source control. In addition to ensuring you don't have to type in all the arguments every single time, this serves as a useful supplement to your documentation for other developers to discover the available options.

blocks|key|3255760|text|我发现一些旧的命令行参数存储在我的启动项目的源文件夹下的MyStartUpProject.csproj.user文件中。删除此文件不起作用，Visual+Studio将其带回给我。我不得不编辑文件中的参数。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3255761|文件中的值未显示在VS、项目属性、调试中。在那里输入值将它们附加到神秘的MyStartUpProject.csproj.user文件中的值。|3255762|entityMap^0|S|S|0|10|S|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I found some old command line arguments stored in a <code>MyStartUpProject.csproj.user</code> file under my startup-project's source folder. Deleting this file didnt work, Visual Studio brought it back for me. I had to edit the arguments in the file.
The values in the file did not show up in VS, Project Properties, Debugging. Entering values there appended them to the values in the mysterious <code>MyStartUpProject.csproj.user</code> file.

blocks|key|3255804|text|在VS2022中，可以调试任何可执行文件。打开包含.exe文件的文件夹|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3255805|3255806|右键单击.exe文件并单击"Set+as+Startup+item“|unordered-list-item|3255807|再次右键单击.exe文件并单击”打开调试和启动设置“|3255808|Add+args+to+launch_schema.json，例如|offset|length|style|BOLD|3255809|<代码>F29|3255810|{
++"version":+"0.2.1",
++"defaults":+{},
++"configurations":+[
++++{
++++++"type":+"default",
++++++"project":+"ffprobe.exe",
++++++"projectTarget":+"",
++++++"name":+"ffprobe.exe",
++++++"args":+[+"C:\\Temp\\test-file"+]
++++}
++]
}|code-block|syntax|javascript|3255811|entityMap^0|0|0|0|0|4|4|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|10|8|@$J|11|K|12|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|14|8|@]|9|@]|A|$S|T]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

In VS 2022 it is possible to debug any executable.
Open a folder containing .exe file
<ul>
<li>Right-click on .exe file and click &quot;Set as Startup item&quot;</li>
<li>Again right-click on .exe file and click &quot;Open Debug and Launch Settings&quot;</li>
<li>Add args to launch_schema.json, e.g.</li>
</ul>
<pre><code>{
 &quot;version&quot;: &quot;0.2.1&quot;,
 &quot;defaults&quot;: {},
 &quot;configurations&quot;: [
 {
 &quot;type&quot;: &quot;default&quot;,
 &quot;project&quot;: &quot;ffprobe.exe&quot;,
 &quot;projectTarget&quot;: &quot;&quot;,
 &quot;name&quot;: &quot;ffprobe.exe&quot;,
 &quot;args&quot;: [ &quot;C:\\Temp\\test-file&quot; ]
 }
 ]
}
</code></pre>

I'm developing a C++ command-line application in Visual Studio and need to debug it with command-line arguments. At the moment I just run the generated EXE file with the arguments I need (like this <code>program.exe -file.txt</code>) , but this way I can't debug. Is there somewhere I can specify the arguments for debugging?

Debugging with command-line parameters in Visual Studio

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在Visual Studio中开发一个C++命令行应用程序，需要使用命令行参数对其进行调试。目前，我只是用我需要的参数运行生成的EXE文件(比如这个program.exe -file.txt)，但是这种方式我不能调试。有没有什么地方我可以指定调试的参数？

问在Visual Studio中使用命令行参数进行调试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Visual Studio中使用命令行参数进行调试EN