-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
UseShellExecute analyzer #707
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before completing the PR, you'll need to run the DocumentationGenerator project to generate the md files.
{ | ||
public void Test() | ||
{ | ||
[||]Process.Start("notepad"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure to understand why it should be reported. UseShellExecute
is only useful when you want to redirect input/output. This method doesn't redirect output, so why do you need to report it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it has a different default value between .NET Framework an .NET core.
Co-authored-by: Gérald Barré <meziantou@users.noreply.github.com>
ae3a538
to
bf255a2
Compare
bf255a2
to
6d3a1a9
Compare
It's probably the number 1 issue I've seen between .NET Framework and .NET Core so I thought that an analyzer might be helpful. Let me know what you think and I'll dig more.