Bug 14152 - Cannot build Jurassic
Summary: Cannot build Jurassic
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-08-21 12:50 UTC by Rodrigo Kumpera
Modified: 2013-08-21 14:09 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 Rodrigo Kumpera 2013-08-21 12:50:51 UTC
I'm trying to build http://jurassic.codeplex.com/ with Xamarin Studio.

It fails to build.

There are multiple issues with this.

Once I click on the top level bar to show the build error I have this on the build log:

Building: Jurassic (Debug)
Performing main compilation...
Build complete -- 1 error, 0 warnings

---------------------- Done ----------------------

Build: 1 error, 0 warnings

I can't find the reason for the failure from above log.

Then the error list pad shows me:

Error: Framework 'Mono / .NET 3.5' not installed. (Jurassic)

Wait, what? I have mono 3.2.2 installed which I'm pretty sure has it.
Comment 1 Rodrigo Kumpera 2013-08-21 14:09:41 UTC
It must have been something funky about my setup.

I though it was a bug in 3.2.2.
So I downgrade to 3.2.1 and 3.2.0, neither have the issue.
Then upgraded to 3.2.2 to confirm the issue - it's gone.
I deleted the source tree and tried again for no avail.

Given there's no direct way to repro this, I'm closing as invalid.