Bug 60578 - Version information in unmanaged location
Summary: Version information in unmanaged location
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 4.0 (d15-5)
Hardware: PC Mac OS
: High normal
Target Milestone: 15.6
Assignee: Bugzilla
Depends on:
Reported: 2017-11-08 19:55 UTC by Chris Hamons
Modified: 2017-11-10 20:53 UTC (History)
4 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 Chris Hamons 2017-11-08 19:55:13 UTC
ObjCRuntime.Constants.Version contains the XM version but we don't record this in a place that is easy to consume in an unmanaged location.

We also don't record the mono version either.

Maybe we could scribble both down downwhere? Info.plist? Some metadata in the launcher? dlsym this to get the XM version and that to get the mono version?
Comment 1 Rodrigo Moya 2017-11-08 19:57:27 UTC
Ideally, we need this before mono 5.6/5.8 gets public, as the profiler needs to know the Mono version (or XM version that we can map to a Mono version) because there was a change in how options are passed to the runtime profiler in Mono > 5.4.
Comment 2 Chris Hamons 2017-11-10 20:53:36 UTC
This is being solved by the runtime folks and not XM specific.