Skip to content

Named Pipe status in .NET 5 #1112

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

Closed
ZoeyR opened this issue Nov 13, 2020 · 3 comments
Closed

Named Pipe status in .NET 5 #1112

ZoeyR opened this issue Nov 13, 2020 · 3 comments
Labels
question Further information is requested

Comments

@ZoeyR
Copy link

ZoeyR commented Nov 13, 2020

I know that allowing gRPC to work over named pipes was on the table for .net 5. Is there any status on that? I saw that UDS was implemented and has a working example but I can't find anything for named pipes.

@ZoeyR ZoeyR added the question Further information is requested label Nov 13, 2020
@BrennanConroy
Copy link
Contributor

Not yet, we're tracking server-side Kestrel support at dotnet/aspnetcore#14207

@JamesNK
Copy link
Member

JamesNK commented Nov 14, 2020

There are extension points in Kestrel and the gRPC client that means named pipes is possible today, but there is no sample at the moment. You would need to figure it out.

There are samples for UDS today. Note that UDS works in modern versions of Windows: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/

@JunTaoLuo
Copy link
Contributor

There hasn't been any response in the past 7 days so we are closing this issue. Please reopen or open a new issue if you you would like to discuss further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants