This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 31%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
VS 16.9.4
Win7-64
Setting command line arguments in:
Debug->Debug Properties->Configuration->Debugging->Command Line Arguments
yield argc ==1, argv[0] == <path>file.exe
My command line arguments are not present. Is there any way to set up command line arguments so that during a debug session I get the arguments? I see from other posts that it is possible so I wonder what I am missing.
Sorry. The correct command is:
Debug->Debug Properties->Configuration->Debugging->Command Arguments
Before entering the arguments, select “All Configurations” and “All Platforms” in Configuration and Platform dropdown lists (or select the settings to be debugged).
Worked just as expected for "All Configurations". I did not find "All Platforms", but w/"All Configurations" my command line seemed to have all the good stuff. argc = # input arguments, argv[0] = <path>file.exe with no input arguments, at least that's what the text/html/json debug visualizers show. I thought that the standard was to show <path>file.exe plus all arguments. Is this not followed VS?
I think you have misunderstood the way command line arguments are passed. The argv array contains an entry for each command line parameter passed. Index 0 is the path to the executable. To obtain the remaining parameters you need to iterate through the array until you have referenced the number of parameters indicated by argc. Don't forget that the array indexes are zero based so the maximum valid index will be one less than the value of.argc.