Add PipeOptions.FirstPipeInstance enum value

[Tarun047]

Added a new Enum Value to represent expose the FILE_FLAG_FIRST_PIPE_INSTANCE flag specific to Windows Kernel API to create named pipes.
Resolve #76984

[ghost]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Added a new Enum Value to represent expose the FILE_FLAG_FIRST_PIPE_INSTANCE flag specific to Windows Kernel API to create named pipes.
Resolve #76984

Author:	Tarun047
Assignees:	-
Labels:	area-System.IO, new-api-needs-documentation
Milestone:	-

[adamsitnik]

@Tarun047 big thanks for your contribution!

Could you please address @stephentoub feedback and let me know whether you could experiment with implementing it also for Unix?

[adamsitnik]

However within the same process we use the static dictionary to check if a server for the given path already exists.
I've changed the code in this area such that it checks if there is firstPipeInstance applied and throw exception.

Great catch!

I've add some comments, we need only a little bit of polishing before merging the PR.

@Tarun047 big thanks for working on it!

[adamsitnik]

However within the same process we use the static dictionary to check if a server for the given path already exists.
I've changed the code in this area such that it checks if there is firstPipeInstance applied and throw exception.

Great catch!

I've add some comments, we need only a little bit of polishing before merging the PR.

@Tarun047 big thanks for working on it!

The concerns have been addressed.

[adamsitnik]

Excellent, great job @Tarun047 !

The failures are unrelated (#86861, dotnet/arcade#11683). I'll re-run the tests that were cancelled due to timeout.

[adamsitnik]

I'll re-run the tests that were cancelled due to timeout.

No luck, will try to repro the timeout locally.

Edit: the timeouts happen in other PRs as well and are being tracked by #76454