Bug 36392 - Need to handle X.Y.Z versions of .NET (4.5.1 for example)
Summary: Need to handle X.Y.Z versions of .NET (4.5.1 for example)
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: mmp ()
Version: Master
Hardware: PC Mac OS
: Normal normal
Target Milestone: 2.8.0 (C7)
Assignee: Chris Hamons
Depends on:
Reported: 2015-11-30 19:15 UTC by Chris Hamons
Modified: 2016-06-02 11:30 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 Chris Hamons 2015-11-30 19:15:07 UTC

    sudo ln -s /Library/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5 /Library/Frameworks/Mono.framework/Versions/Current/lib/mono/4.5.1

works as a work around for now.
Comment 1 Timothy Risi 2015-12-04 00:34:59 UTC
Fixed on master / 766101f88bdb00e4ca4ea63a218c9a21975dcca5
Comment 2 Rajneesh Kumar 2016-06-02 11:30:09 UTC
I have checked this issue with the cycle 7 build: 

and observed that this issue no l longer exist with this build. Now user is able to build the application with target framework: .Net framework 4.5.1 successfully.

Screencast: http://www.screencast.com/t/3CoDdCBhuIRT

This issue has been fixed , hence I am closing this issue.