Bug 14062 - Compiling MonoDevelop in Xamarin Studio
Summary: Compiling MonoDevelop in Xamarin Studio
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.12
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-08-18 08:02 UTC by Krzysztof
Modified: 2014-10-07 05:46 UTC (History)
2 users (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 NORESPONSE

Description Krzysztof 2013-08-18 08:02:59 UTC
After compiling MonoDevelop (4.1.7) project with Xamarin Studio error below shows:

Error CS1705: Assembly `Microsoft.Build.Utilities.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' references `Microsoft.Build.Framework, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version number than imported assembly `Microsoft.Build.Framework, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' (CS1705) (MonoDevelop.Projects.Formats.MSBuild.v3.5)
Comment 1 Marius Ungureanu 2013-11-25 07:09:43 UTC
Is this still an issue? I think this got fixed a while back.
Comment 2 Marius Ungureanu 2014-10-07 05:46:41 UTC
This has been open for quite a while with no response. It works for me.