Bug 14539 - MonoGame.Tests.MacOS project no longer builds
Summary: MonoGame.Tests.MacOS project no longer builds
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Mac Add-in ()
Version: 4.1.10
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2013-09-08 17:37 UTC by Brandon Bremen
Modified: 2015-04-10 15:03 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Brandon Bremen 2013-09-08 17:37:28 UTC
This was building with the 4.0.12 beta. We upgraded to the Alpha to work around a bug and it doesn't build.

I am running on Mac OS 10.8.4.

MonoGame.Tests.MacOS.csproj: Error: /Users/brandon/src/MonoGame-fork/Test/MonoGame.Tests.MacOS.csproj: /Users/brandon/src/MonoGame-fork/Test/MonoGame.Tests.MacOS.csproj could not import "$(MSBuildExtensionsPath)\Mono\MonoMac\v0.0\Mono.MonoMac.targets" (MonoGame.Tests.MacOS)

The path mentioned in the error appears in the following line of the csproj file:

<Import Project="$(MSBuildExtensionsPath)\Mono\MonoMac\v0.0\Mono.MonoMac.targets" />
Comment 1 Jeffrey Stedfast 2013-09-08 18:25:37 UTC
how are you trying to build?
Comment 2 Brandon Bremen 2013-09-08 18:32:12 UTC
Open MonoGame/Test/MonoGame.Tests.MacOS.sln and press cmd-b. Debug configuration is active and MonoGame.Tests.MacOS is currently the active project.
Comment 3 Brandon Bremen 2013-09-08 18:33:19 UTC
I am building from the MonoGame develop branch commit 626714b.

It builds fine after downgrading the 4.0.12 on the beta channel.
Comment 4 Jeffrey Stedfast 2013-09-08 19:23:13 UTC
Did you enable experimental xbuild/msbuild support or anything?

It shouldn't even care about the dummy Mono.MonoMac.targets file if it's using the standard build system.

That .targets file doesn't exist and never should have gone into the .csproj files anyway. It's a bug that it's even there.
Comment 5 Brandon Bremen 2013-09-08 19:31:45 UTC
I'm not sure how to check which build system it is using. I do see in the Project Options that "Use MSBuild build engine (recommended for this project type)" is checked.

Thanks for letting me know that Import shouldn't be in the csproj file. I will submit a patch to remove it from MonoGame.
Comment 6 Jeffrey Stedfast 2013-09-08 20:15:51 UTC
Uncheck that checkbox and I bet it will start working again.
Comment 7 Brandon Bremen 2013-09-09 00:42:10 UTC
Making that change does cause it to start building without error.

I diffed the csproj file after unchecking that box and the following line was added which did not exist before:

<UseMSBuildEngine>False</UseMSBuildEngine>

Does that mean MSBuild will now be the default build engine for project types that support it?
Comment 8 Jeffrey Stedfast 2013-09-09 07:14:39 UTC
I think that was a change that was made recently. But now that I know what caused this, I'll reassign appropriately. That change is likely to cause breakage among every monomac project :-(

Thanks for reporting this!
Comment 9 Chris Hamons 2015-04-10 15:03:03 UTC
Sorry for the long delay in responding to this bug. 

I believe this issue has been fixed in newer builds.

Please reopen if this issue still exists and apologies again on the delay.