Bug 8438 - MfA should use MSBuild framework on Mac
Summary: MfA should use MSBuild framework on Mac
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.0
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2012-11-15 15:55 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-06-28 03:28 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 Mikayla Hutchinson [MSFT] 2012-11-15 15:55:17 UTC
MfA should use MSBuild frameworks on Mac the way it does on Windows, to simplify the targets and so that MonoDevelop no longer has to redefine all the frameworks.

MfA should install the same framework definition files it does on Windows, but into /Library/Frameworks/Mono.framework/External/xbuild-frameworks. Note that it doesn't have to move the dlls, since with Mono (not .NET) it's possible for custom frameworks definition files to point to another directory containing the actual assemblies using the TargetFrameworkDirectory attribute - see MonoTouch/v1.0/RedistList/FrameworkList.xml for an example.

Then the GetFrameworkPaths and ResolveAssemblyReferencesDependsOn overrides could be removed from the Novell.MonoDroid.Common.targets, and assembly resolution would work the same way it does in Windows. And all the framework definition files could be removed from MonoDevelop.