Skip to content

A project to show differences between .Net Core 2.0 and 2.1 when using NamedPipeServerStream.EndWaitForConnection

License

Notifications You must be signed in to change notification settings

liserdarts/NamedPipeServerStreamTest

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This project shows some behaviour differences with System.IO.Pipes.NamedPipeServerStream between .NET Core 2.0 and 2.1-Preview1. Look in Output.md to see this program output from different platforms and versios of .NET Core.

Differences between 2.0 and 2.1-Preview1.

When using .NET Core built from the v2.1-Preview1 branch some new exceptions are thrown.

SocketException

With 2.1-Preview1 System.Net.Sockets.SocketException is thrown on one background thread calling NamedPipeServerStream.EndWaitForConnection. This is new behaviour.

NullReferenceException

On 2.1-Preview1/Debian9/x86 there is also a System.NullReferenceException on a background thread. This comes out of System.Threading.ThreadPoolWorkQueue.Dispatch() and I don't know of any way to catch it. This is an unhandled exception and will cause the program to crash.

ObjectDisposedException

With 2.1-Preview1 there is a System.ObjectDisposedException when calling NamedPipeServerStream.EndWaitForConnection. This was expected behaviour in 2.0 even though this program does not show it.

About

A project to show differences between .Net Core 2.0 and 2.1 when using NamedPipeServerStream.EndWaitForConnection

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published