Bug 27578 - Missing bindings for NSLock and related
Summary: Missing bindings for NSLock and related
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.6.0
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: 8.13 (C6 alpha)
Assignee: Paola Villarreal
Depends on:
Reported: 2015-03-02 17:23 UTC by Dave Dunkin
Modified: 2015-04-10 21:59 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Dave Dunkin 2015-03-02 17:23:52 UTC
There are no bindings for NSLock, NSConditionLock, NSRecursiveLock, or NSCondition.
Comment 1 Miguel de Icaza [MSFT] 2015-03-30 12:27:25 UTC
What is the use case for these, when C# surfaced a comprehensive set of APIs that provide similar features?
Comment 2 Dave Dunkin 2015-03-30 13:01:10 UTC
The use case is binding to Objective-C code that uses NSLock in its API.
Comment 3 Paola Villarreal 2015-04-10 21:59:39 UTC
Bindings done on master 66da2202490413a57d325fb4993e9000f94c62ef