-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DebugConsole: make powershell work interactively like CMD #877
Comments
I've played with this before and the best I've been able to do is call powershell -File - |
Wow, I just tried that in the new interactive console and it actually works! Check out this session:
|
I tried prompting for input from PS and that blew up:
|
interesting, that seems related to how Azure is handling the Console Win32 APIs because it's completely different from OnPrem. I will open a bug for Stephen. on the other hand, it seems that powershell already has some form of web access http://technet.microsoft.com/en-us/library/hh831417.aspx |
@davidebbo since powershell works if you type "powershell -file -" instead of just "powershell" do you think it would be better if we just rewrite "powershell" to "powershell -file -" behind the scenes, display a sort of warning saying something like "type powershell -file - instead of powershell" or have a different link for powershell console all together? |
Yes, I suppose we could do that. Maybe a better approach is to have buttons in the DebugConsole that lets the user select what shell they want. The thinking is that a powershell user should be able to directly be in powershell, as opposed to starting in cmd and having to type 'powershell' to get there. Implementation wise, it could be a query string param that choose the mode, e.g. |
Powershell doesn't seem to work with stdout and stdin redirection like cmd.exe. I am not sure what the issue is with powershell, but they might have more robust APIs to accomplish this. We need to investigate this with powershell team.
@Gissues:{"order":78.84615384615373,"status":"backlog"}
The text was updated successfully, but these errors were encountered: