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.

Sign up for GitHub

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

Jump to bottom

[Tracking] New APIs for named synchronization objects #112868

Open

1 of 4 tasks

kouvel opened this issue Feb 24, 2025 · 1 comment

Open

1 of 4 tasks

[Tracking] New APIs for named synchronization objects #112868

kouvel opened this issue Feb 24, 2025 · 1 comment

Assignees

Labels

area-System.Threading

Milestone

Member

kouvel commented Feb 24, 2025

- API proposal: [API Proposal]: New overloads for named wait handles that enable creating/opening user-specific synchronization primitives #102682 (comment)
- Implement new APIs
- PR: Add the CurrentUserOnly and CurrentSessionOnly options for named Mutex, Semaphore, and EventWaitHandle #112213
- Document new APIs, and update docs of other APIs
- Deprecate the old named APIs (ones that have a name argument and no options argument)

The text was updated successfully, but these errors were encountered:

kouvel added the area-System.Threading label

kouvel added this to the 10.0.0 milestone

kouvel self-assigned this

Contributor

dotnet-policy-service bot commented Feb 24, 2025

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment