F5 breaks when project command-line includes a > character

F5 breaks when project command-line includes a > character by dmatson

Closed

as Deferred Help for as Deferred

Type:	Bug
ID:	780049
Opened:	2/26/2013 11:27:49 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

VS doesn't behave correctly when the project properties command-line arguments includes an argument with the greater-than character (>). This behavior is particularly problematic when putting a password in as a command-line argument (a password may have a > character in it).

1.     Create a new Console App (VS 2012).
2.     Add the following lines to Main:
Console.WriteLine(args[0]);
Console.Read();
3.     On project properties (Debug tab), set the command-line arguments to:
Pass>word
4.     Execute the application (Ctrl+F5). Note that it works (the output is "pass>word").
5.     Debug the application (F5). Note that it doesn’t work. Specificially, args[0] is "pass"; the output is redirected to "word".

Details (expand)

Visual Studio 2012

1.     Create a new Console App (VS 2012).
2.     Add the following lines to Main:
Console.WriteLine(args[0]);
Console.Read();
3.     On project properties (Debug tab), set the command-line arguments to:
Pass>word
4.     Execute the application (Ctrl+F5). Note that it works (the output is "pass>word").
5.     Debug the application (F5). Note that it doesn’t work. Specificially, args[0] is "pass"; the output is redirected to "word".

English

Windows 8

English

args[0] is only a portion of the argument specified; output is redirected to a file

args[0] is the full argument specified; output is not redirected to a file

0 attachments

Posted by Microsoft on 3/27/2013 at 3:08 PM

Thank you for the valuable feedback. Though we will not have a chance to address this issue in Visual Studio 2012, we will consider this feedback when planning for future versions of Visual Studio. Investments in this area will be weighed against the impact of other customer reported issues.

Posted by Microsoft on 2/26/2013 at 10:37 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 2/26/2013 at 11:50 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)