Modify the wpf to connect to the mcp server using the stdio method #694
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.
Hi maintainers 👋,
I've opened this PR to fix an issue where attempting to set
Console.InputEncoding
andConsole.OutputEncoding
in non-console applications (like WPF) throws aNotSupportedException
, which causes the connection to the MCP server via stdio to fail.This change adds a check to detect whether the current environment supports console I/O before applying encoding settings, preventing the exception in GUI applications such as WPF.
✅ The fix has been tested locally in a real WPF application and resolves the connection issue.
✅ No breaking changes are introduced.
Could someone please review this when you have time? It would help enable smoother integration of the SDK in WPF and other desktop applications.
Thanks for your work on the project! 🙏
Modify the wpf to connect to the mcp server using the stdio method
Motivation and Context
WPF uses STDIO to connect to MCP server and throws an exception
How Has This Been Tested?
yes,i have tested in my wpf project
Breaking Changes
no
Types of changes
Checklist
Additional context