Home Dashboard Directory Help
Search

Ctrl+F5 changes command-line when it includes a quoted > character by dmatson


Status: 

Closed
 as Deferred Help for as Deferred


1
0
Sign in
to vote
Type: Bug
ID: 780050
Opened: 2/26/2013 11:30:33 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

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).

When trying to work around the VS F5 behavior, this behavior is even more surprising.

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 (include the quotes):
"Pass>word"
4.     Debug the application (F5). Note that it works (the output is "pass^>word").
5.     Execute the application (Ctrl+F5). Note that it dosen’t work. Specifically, args[0] is now different; it outputs "pass^>word" instead of "pass>word", silently adding a ^ character before the > character.
Details
Sign in to post a comment.
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:41 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)
Sign in to post a workaround.