Stop the Debug Log harassment for linux users #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses an issue related to debug logging in the codebase that specifically affects Linux users. The existing code snippet includes a catch block that throws a System.ComponentModel.Win32Exception when a command is not found or not accessible.
The updated code has modified the catch block to catch a general Exception instead. This change allows the code to continue executing in case of any exception, ensuring that Linux users are not bombarded with unnecessary debug log messages. A new debug log message has also been added to notify when a compatible dotnet command cannot be found.
These modifications enhance the code's compatibility with Linux systems and improve the user experience by reducing unnecessary debug log output.