Page Needs major reworking
- Dominant language
- No language data
- Stars
- 4.8k
- Forks
- 6.1k
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 370
Description
The code sections are too long. They try to do too much and are not trimmed to show the main point of using named pipes for IPC. They are also too wide. Though my browser is wide enough to hold the full width of the code, the panel with the code snippet is so narrow that I have to side-scroll. But because it is so long, the side-scroll bar is below the bottom of the browser window. When I scroll far enough down to scroll horizontally, I can't see the code that I was trying to read.
Are we having fun yet?
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: b86675e7-4bfb-707d-fe36-c02da2023342
* Version Independent ID: ee821843-1cad-0455-f278-1194b88dd0b0
* Content: [How to: Use Named Pipes for Network Interprocess Communication](https://learn.microsoft.com/en-us/dotnet/standard/io/how-to-use-named-pipes-for-network-interprocess-communication)
* Content Source: [docs/standard/io/how-to-use-named-pipes-for-network-interprocess-communication.md](https://github.com/dotnet/docs/blob/main/docs/standard/io/how-to-use-named-pipes-for-network-interprocess-communication.md)
* Product: **dotnet-fundamentals**
* GitHub Login: @adegeo
* Microsoft Alias: **adegeo**
Contributor guide
Assessment
This issue has not been assessed yet.