Bug 30689 - Adding PCL gives - Assembly `System.IO' with the same identity has already been imported
Summary: Adding PCL gives - Assembly `System.IO' with the same identity has already be...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: MSBuild ()
Version: 2.0.0
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-06-02 15:42 UTC by Chris Hamons
Modified: 2017-03-16 15:43 UTC (History)
3 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 FIXED

Description Chris Hamons 2015-06-02 15:42:14 UTC
- New Unified Project
- Add nuget - linqtotwitter 
- Build


CSC: error CS1703: An assembly `System.IO' with the same identity has already been imported. Consider removing one of the references
CSC: error CS1703: An assembly `System.Runtime' with the same identity has already been imported. Consider removing one of the references
CSC: error CS1703: An assembly `System.Threading.Tasks' with the same identity has already been imported. Consider removing one of the references


Removing the references under From Packages "fixes" the issue, but should be unnecessary
Comment 2 Chris Hamons 2017-03-16 15:43:15 UTC
This has been fixed in at least XM 3.0.