Bug 11112 - NSRunningApplication.CurrentApplication shouldn't ensure it runs on UI thread
Summary: NSRunningApplication.CurrentApplication shouldn't ensure it runs on UI thread
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 1.0.x
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-13 08:31 UTC by Marek Habersack
Modified: 2013-05-15 00:00 UTC (History)
1 user (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 Marek Habersack 2013-03-13 08:31:40 UTC
Code similar to:

NSRunningApplication.CurrentApplication.InvokeOnMainThread (() => Console.WriteLine ("hello"));

will throw AppKitThreadAccessException since CurrentApplication getter calls EnsureUIThread ()
Comment 1 Miguel de Icaza [MSFT] 2013-05-15 00:00:35 UTC
Fixing that

But in the meantime, just use another NSObject.