Files
mono/mcs/class/System.Core/System.IO.Pipes/NamedPipeClientStream.NotSupported.cs
Filip Navara 0f0e31842f System.IO.Pipes from CoreFX (#9573)
Rework of #5448, contributes to #7143.

The anonymous pipes were tested on macOS, build was tested only on few configurations (hoping to solve some issue through Jenkins builds). Named pipe tests get stuck on macOS, but it may be unrelated Xunit issue and needs some proper debugging.

@Therzok, do you know of anything else that is missing for parallel MSBuild? Do you have some test environment for it by chance?
2018-07-24 10:19:18 +02:00

42 lines
1.1 KiB
C#

using Microsoft.Win32.SafeHandles;
using System.ComponentModel;
using System.Diagnostics.CodeAnalysis;
using System.Runtime.InteropServices;
using System.Net.Sockets;
using System.Security;
using System.Threading;
using System.Security.Principal;
namespace System.IO.Pipes
{
/// <summary>
/// Named pipe client. Use this to open the client end of a named pipes created with
/// NamedPipeServerStream.
/// </summary>
public sealed partial class NamedPipeClientStream : PipeStream
{
public NamedPipeClientStream (string serverName, string pipeName, PipeAccessRights desiredAccessRights, PipeOptions options, TokenImpersonationLevel impersonationLevel, HandleInheritability inheritability)
: base (PipeDirection.In, 0)
{
throw new PlatformNotSupportedException ();
}
private bool TryConnect (int timeout, CancellationToken cancellationToken)
{
throw new PlatformNotSupportedException ();
}
public int NumberOfServerInstances
{
get {
throw new PlatformNotSupportedException ();
}
}
private void ValidateRemotePipeUser (SafePipeHandle handle)
{
throw new PlatformNotSupportedException ();
}
}
}