10000 See why script errors are not correctly reported to console, they are only reported to trace output · Issue #53 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

See why script errors are not correctly reported to console, they are only reported to trace output #53

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.

Sign up for GitHub

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

Jump to bottom
Closed
andyleejordan opened this issue Jan 22, 2016 · 0 comments
Closed

See why script errors are not correctly reported to console, they are only reported to trace output #53

andyleejordan opened this issue Jan 22, 2016 · 0 comments
Assignees
@andyleejordan

Comments

@andyleejordan
Copy link
Member

Good example is this Example #1 Input Command ThatDoesNotExist This should result in an error message visible in the console output. Example #2 Input Import Module PowerShell.Commands.Utility Get Location ParamThatDoesNotExist This should result in an error message visible in the console output. Update the root problem was the console we had wasn't catching all the exceptions, but this got fixed for free when we rewrote the console. VSO create date - 6/5/2015 10:46:00 VSO closed date - 7/6/2015 12:53:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andyleejordan andyleejordan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andyleejordan
0