Bug 13513 - Consider adding a reference to assembly 'system.core, version='
Summary: Consider adding a reference to assembly 'system.core, version='
Status: RESOLVED DUPLICATE of bug 13464
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-07-26 12:29 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2013-07-26 16:58 UTC (History)
2 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 Brendan Zagaeski (Xamarin Team, assistant) 2013-07-26 12:29:54 UTC
From a user:

I upgraded to the latest stable version of Xamarin Studio yesterday. I had a project that compiled fine, and now I'm getting some errors when building.

[After running https://github.com/rolfbjarne/iOSRefUpdater on the third party assemblies...]

I'm getting errors now during build telling me to consider adding a reference to assembly 'system.core, version='

[Next step]

I'll see if I can get through all of the external assemblies and recompile them.
Comment 3 Marek Safar 2013-07-26 16:58:08 UTC

*** This bug has been marked as a duplicate of bug 13464 ***