Bug 4365 - Cannot build MonoDroid applications
Summary: Cannot build MonoDroid applications
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-04-10 07:42 UTC by Alan McGovern
Modified: 2012-04-11 08:57 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 Alan McGovern 2012-04-10 07:42:45 UTC
I believe commit a8b679fbeac4 broke the compilation of MonoDroid projects. My monodroid csproj specifies:

<Import Project="$(MSBuildExtensionsPath)\Novell\Novell.MonoDroid.CSharp.targets" />

MonoDevelop now expands that to:

Comment 1 Jeffrey Stedfast 2012-04-10 15:25:26 UTC
fixed in mono-2-10 and master
Comment 2 Alan McGovern 2012-04-10 20:03:10 UTC
This is a big behavioural change as it means that monodevelops xbuild support will now only work with unreleased versions of mono/xbuild. Would it be possible to limit the alternative msbuild path fixes when a portable .net project is being built?
Comment 3 Jeffrey Stedfast 2012-04-10 22:31:45 UTC
The problem is that there is no way to find out if that is the case
Comment 4 Alan McGovern 2012-04-11 04:57:30 UTC
I assume this is because we need to tell xbuild where the targets file for portable .net projects is. If so, would it be worth flipping things around by shipping the targets file with mono itself? That way we could place the file in the normal directory which means xbuild would work just fine for people with existing versions of Mono.
Comment 5 Jeffrey Stedfast 2012-04-11 08:57:58 UTC
At this point we probably could. The original intention was to get around needing to do that, but I guess we can't.