When creating named pipes using the NamedPipeClientStream or NamedPipeServerStream classes of dotnet core, the associated "pipe" (which appears to actually be a socket) has "CoreFxPipe_" added to the front of the file name automatically.
Is there a non-hacky way to prevent this behavior? I would simply like the file name to be exactly the name I provide to the constructor.
In the dotnet core documentation, it describes the following constructor:
NamedPipeServerStream(String)
Initializes a new instance of the NamedPipeServerStream class with the specified pipe name.
But, for reasons described above, this description appears to be misleading at best.