# Steps to reproduce
1. Use an assembly that references “System.Data.Common, Version=220.127.116.11”. Example: Microsoft.Data.Sqlite which is built for netstandard1.3 and references this asembly.
2. Install via NuGet.
3. Add instance of type that references a system.data.common type. (e.g. Microsoft.Data.Sqlite.SqliteConnection)
4. Add reference to System.Data
# Expected behavior
Compiler should unify System.Data.Common to types from System.Data
# Actual behavior
The type `System.Data.Common.DbConnection' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Data.Common, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
# Supplemental info
MSBuild in VS 2015 works fine. This only applies to Xamarin Studio on OSX
# Test environment (full version information)
Xamarin Studio Business
Version 6.0.2 (build 69)
Installation UUID: 4a799370-fcb0-4bf4-afd8-de1edaf4ec61
Mono 4.4.2 (mono-4.4.0-branch-c7sr1/4dff7a3) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 404020004
Apple Developer Tools
Xcode 7.3 (10183.3)
Version: 22.214.171.124 (Xamarin Business)
Build date: 2016-07-18 15:40:25-0400
Version: 126.96.36.199 (Xamarin Business)
Android SDK: /Users/namc/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
SDK Tools Version: 25.1.2
SDK Platform Tools Version: 24.0.0
SDK Build Tools Version: 23.0.2
Java SDK: /usr
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
Android Designer EPL code available here:
Xamarin Android Player
Version: 188.8.131.52 (Xamarin Business)
Release ID: 600020069
Git revision: 9e0e96423ed474edf179c070b64ad03634012766
Build date: 2016-07-15 16:53:35-04
Xamarin addins: affe3f734f88d4f1ca34083ae3dde40dfc53d07a
Build lane: monodevelop-lion-cycle7-sr1
Mac OS X 10.11.5
Which kind of project are you adding the reference to? What's the target framework?
@Lluis this happens when using a Xamarin.iOS or Xamarin.Android application.
How are you adding Microsoft.Data.Sqlite to a Xamarin project? netstandard libraries are not supported by Xamarin.iOS or Xamarin.Android.
Via NuGet. The latest beta release adds initial support .NET Standard.
Setting this bug CONFIRMED, since I was able to reproduce this issue with latest C8 builds.
In attachments, you will find a sample app where PCL app references System.Data.Common NugGet build for .netstandard 1.3.
Created attachment 16842 [details]
Fixed in master and Mono 4.6
They should have the fix. Could you attach your test project
The issue is actually somewhere else. mcs is compatible with native csc (pre-Roslyn) but not with Roslyn which does better job in checking required dependencies.
The error is about missing reference not about unification.
Same error can be triggered with Roslyn if you use more realistic example like
var oo = new PCL.CustomException();
This is not easy to fix with current design, would probably have to introduce LookupType path as alternative to Resolve
Notice (2018-05-21): bugzilla.xamarin.com will be
switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.
Please join us on
Visual Studio Developer Community and
GitHub to continue tracking
issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs and copy them to the new
locations as needed for follow-up. The See Also field
on each Bugzilla bug will be updated with a link to its new location
After Bugzilla is read-only, if you have new information to add for a
bug that does not yet have a matching issue on Developer Community or
GitHub, you can create a follow-up issue in the new location. Copy and
paste the title and description from this bug, and then add your new
details. You can get a pre-formatted version of the title and
In special cases you might also want the comments:
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.